Java Data Objects – link to JavaBeans

It is not possible to add the new link because it would replace an existing, longer link.

Line 1:

== JDO vs. EJB3 vs. JPA ==

[[Enterprise JavaBeans]] 3.0 (EJB3) specification also covered persistence, as had EJB v2 with [[Entity Bean]]s. There have been standards conflicts between the two standards bodies in terms of pre-eminence. JDO has several commercial implementations.

Enterprise [[JavaBeans]] 3.0 (EJB3) specification also covered persistence, as had EJB v2 with [[Entity Bean]]s. There have been standards conflicts 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 <code>javax.persistence</code> package, and was first specified in a separate document within the EJB3 spec [http://www.jcp.org/en/jsr/detail?id=220 JSR 220], but was later moved to its own spec [http://www.jcp.org/en/jsr/detail?id=317 JSR 317]. Significantly, <code>javax.persistence</code> 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 targeted to RDBMS datastores (although there are several JPA providers that support access to non-relational datastores through the JPA API, such as DataNucleus and ObjectDB).

@@ Line 1: / Line 1: @@
 == JDO vs. EJB3 vs. JPA ==
-[[Enterprise JavaBeans]] 3.0 (EJB3) specification also covered persistence, as had EJB v2 with [[Entity Bean]]s. There have been standards conflicts between the two standards bodies in terms of pre-eminence. JDO has several commercial implementations.
+Enterprise [[JavaBeans]] 3.0 (EJB3) specification also covered persistence, as had EJB v2 with [[Entity Bean]]s. There have been standards conflicts 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 <code>javax.persistence</code> package, and was first specified in a separate document within the EJB3 spec [http://www.jcp.org/en/jsr/detail?id=220 JSR 220], but was later moved to its own spec [http://www.jcp.org/en/jsr/detail?id=317 JSR 317]. Significantly, <code>javax.persistence</code> 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 targeted to RDBMS datastores (although there are several JPA providers that support access to non-relational datastores through the JPA API, such as DataNucleus and ObjectDB).