When to use JDO with Java application servers

If the data in your database is complex or the mapping from the relational model to the Java object model is complex, it is best to use JDO with Java application servers instead of JDBC or SQLJ. This would mean that the mapping can be placed in one location outside of your application or application server as opposed to mapping data in multiple locations. See JDBC data conversion (new window) and SQLJ data conversion (new window). Having to map data in only one location simplifies both development and maintenance.

If you have new data and do not have an existing database that requires data mapping, take a look at EJB accelerators (new window).

For more information on JDO issues related to data mapping, see JDO data conversion (new window)

Also, if you are not familiar with the concept of complex data, see complex data (new window).

 

Web Services and Service-Oriented Architectures
Online articles>
Consulting
Mentoring
Speaking
Suggested programs
Stencils for the Savvy Manager's Guide
Links
Mail list
Privacy policy
Sitemap
Contact
Web Services articles
XML standards and vocabularies
Application server articles>
Database concepts and standards
Object database articles
Relational database articles
Object-relational mapping articles
XML database articles
XML middleware articles
Article Sponsorship
Reprint policy
Application server definition
When an application server should be used
Application server achitectures>
J2EE architecture solutions
Article suggestions
Using JDBC with application servers
Using SQLJ with application servers
Using JDO with application servers>
Using EJB accelerators with application servers
JDO data conversion
When to use JDO with Java application servers>

 

Copyright © 2000-2008 Barry & Associates, Inc. All Rights Reserved.
You can use this material for your work or classes. Click here for our reprint policy.
www.service-architecture.com

 

 Information on becoming a sponsor

 

 

Google

 

Barry & Associates, Inc.