Java Data Objects
From Wikipedia, the free encyclopedia
Java Data Objects (JDO) is a specification of Java object persistence. One of its features is a transparency of the persistent services to the domain model. JDO persistent objects are ordinary Java programming language classes; there's no requirement for them to implement certain interfaces or extend from special classes. JDO 1.0 was developed under the Java Community Process as JSR 12. JDO 2.0 was developed under JSR 243 and was released on May 10th, 2006. JDO 2.1 was completed in Feb 2008, developed by the Apache JDO project. JDO 2.2 was released in October 2008. JDO 2.3 is in its planning stage.
Object persistence is defined in the external XML metafiles, which may have vendor-specific extensions. JDO vendors provide developers with enhancers, which modify compiled Java class files so they can be transparently persisted. (Note that byte-code enhancement is not mandated by the JDO specification, although it is the commonly used mechanism for implementing the JDO specification's requirements.) Currently, JDO vendors offer several options for persistence, e.g. to RDBMS, to OODB, to files.
JDO enhanced classes are portable across different vendors' implementation. Once enhanced, a Java class can be used with any vendor's JDO product.
JDO is integrated with Java EE in several ways. First of all, the vendor implementation may be provided as a JEE Connector. Secondly, JDO may work in the context of JEE transaction services.
Contents |
[edit] JDO vs. EJB3
Enterprise Java Beans 3.0 (EJB3) specification also covered persistence, as had EJB v2 with Entity Beans. There has been standards conflict between the two standards bodies in terms of pre-eminence. JDO has several commercial implementations.
In the end, persistence has been "broken out" of "EJB3 Core", and a new standard formed, the Java Persistence API (JPA). JPA uses the javax.persistence package, and is specified in a separate document within the EJB3 JSR 220. Significantly, javax.persistence will not require an EJB container, and thus will work within a Java SE environment as well, as JDO always has. JPA, however, is an Object-relational mapping (ORM) standard, while JDO is both an Object-relational mapping standard and a transparent object persistence standard. JDO, from an API point of view, is agnostic to the technology of the underlying datastore, whereas JPA is being oriented totally around RDBMS datastores.
Leading JDO commercial implementations and open source projects will and some already are offering a JPA API implementation as an alternative access to their underlying persistence engines, formerly exposed via JDO only in the original products. There are many open source implementations of JDO.
[edit] New Features in JDO Version 2 Not Found In Version 1
- Disconnected Object Graphs concept
- Standardized ORM Mapping Descriptors (for ORM-based JDO Implementations)
- JDOQL Enhancements (Single String Form; more String, Map & Math methods support mandated)
- Get e.g. a java.sql.Connection from javax.jdo.PersistenceManager
- More: Named Queries (pm.newNamedQuery), FetchPlan, Sequence, Delete by Query, multiple User Objects on PM
[edit] See also
[edit] External links
[edit] Specifications
[edit] Implementations
[edit] Open Source
- JPOX – Open Source JDO 2 reference implementation (ORM)
- DataNucleus Access Platform – Persistence to RDBMS, db4o, LDAP, XML, Excel, NeoDatis, JSON, OpenDocumentFormat
- Orient Technologies – ODBMS with JDO interface
- JDOinstruments – ODBMS with JDO interface
- Speedo – Open Source JDO 2 implementation (ORM)
