202 JDO implementations schema. Enterprises can use this
202 JDO implementations schema. Enterprises can use this approach for migration to a JDO layer above the existing enterprise data layer for easy maintenance and robustness. The schema of the existing enterprise database is captured and an object model created automatically by Frontier ReModeler for JDO. From this object model, a JDO application that uses the existing database schema is created. 12.3.3.3 Frontier DeployDirect for JDO (Class Enhancement) Normal non-persistent Java classes can be made persistence-capable through Frontier DeployDirect for JDO, which includes a JDO enhancer and a mapping tool for mapping the enhanced classes to a relational database schema. The mapping process is totally automated and GUI based and allows much flexibility in terms of fine-tuning the default mapping schema. 12.3.3.4 Frontier DeployDirect for JDO (Bridge Pattern) Java Applications that use a database schema and that want to migrate to the JDO standard, while retaining the existing Java Code and the database schema, can use the Bridge pattern supported by Frontier DeployDirect for JDO. This approach provides a bridge between legacy applications and JDO standards by enhancing the existing Java classes to become persistence-capable and mapping these enhanced classes to the existing database schema through a GUI interface. This provides maximum reusability, wherein both the existing Java Code and the database schema are migrated to the JDO standard and become part of the new JDO application. 12.3.4 Supported data stores FrontierSuite for JDO targets JDBC compliant relational databases, specifically: Oracle MS SQL Server DB2 PointBase Cloudscape MS Access 12.3.5 Supported application servers FrontierSuite for JDO currently supports the following J2EE application servers: Weblogic WebSphere
Note: If you are looking for high quality webhost to host and run your jsp application check Vision jsp hosting services