Using JDO with application servers

If you are using existing databases with an application server, you might want to consider a Java Data Objects (JDO) interface. JDO allows you to move the mapping of data from the application server or application side to one location. This differs from using JDBC with application servers (new window) or using SQLJ with application servers (new window). With JDBC, the mapping needs to be done above the JDBC interface. With JDO, the mapping is done below the JDO interface.

JDO is considered a form of transparent persistence. For more information on how transparent persistence compares to JDBC, see transparent persistence vs. JDBC call-level interface (new window).

Also, be sure to check out how JDO can be part of integrated J2EE architecture solutions (new window).

Using JDO, as shown in this diagram, will require data conversion between the interface and the database. See JDO data conversion.

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