Sun creates new Persistence API: EJB & JDO join forces

Sun creates new Persistence API: EJB & JDO join forces
Posted By: Dion Almaer on September 24, 2004 @ 05:33 PM
An open letter from Sun, to the community, has been released. The letter tal
ks about how a new specification, RI, and TCK will be placed under the JSR-2
20 (EJB 3) group. JDO experts will join this effort, which will be based on
the EJB 3 early draft as a starter.
Sun is hoping that the entire community can get behind the goal of ONE persi
tence API for J2SE and J2EE.
They are encouraging us to read through all of the material to understand wh
at is going to happen to the future of persistence in Java.
A Letter to the Java Technology Community
For years, the Enterprise JavaBeans(tm) (EJB(tm)) and Java(tm) Data Objects
(JDO) specifications have evolved independently as they addressed different
sets of requirements. The core of both specifications, however, includes per
sistence technology. Even to this day, the data persistence models in EJB an
d JDO differ significantly. This divergence has caused confusion and debates
 among Java developers, and is not in the best interest of the Java communit
y. Consequently, requests to put an end to this unwanted divide have poured
in from members of the Java community. In response to these requests, Sun Mi
crosystems is leading a community effort to create a single POJO (Plain Old
Java Object) persistence model for the Java community. This effort will stre
ngthen community solidarity.
Starting this reconciliation effort now is very timely given that both the E
JB and JDO specifications are going through significant revisions. As specif
ication leads for EJB 3.0 (JSR-220) and JDO 2.0 (JSR-243), we have jointly c
reated the following plan to move this community effort forward:
This is a community effort. We are expanding the JSR-220 Expert Group to inc
lude some members from the JSR-243 Expert Group. By joining forces, we will
bridge the two communities and leverage the know-how in both groups. The cur
rent JSR-220 specification lead will remain unchanged.
The work to define a single POJO persistence model for the Java community wi
ll be done under JSR-220 starting from the existing JSR-220 Early Draft.
The technical objective for this new POJO persistence model is to provide a
single object/relational mapping facility for all Java application developer
s that works in both J2SE and J2EE. The work will be done within the J2EE 5.
0 time frame.
The new POJO persistence model will be delivered by JSR-220 as a separate sp
ecification, Reference Implementation, and Technology Compatibility Kit, usa
ble independently of EJB 3.0.
As currently planned, the scope of JSR-243 will include maintenance to JDO 1
.0.1 and enhancements to JDOQL. Additionally, the JDO expert group will aim
to deliver JDOQL that would work with the new POJO persistence model so thos
e with a preference for JDO query style can leverage the new common persiste
nce API. The current JSR-243 specification lead will remain unchanged.
We believe this is a unique opportunity for the Java community to create a c
ommon POJO persistence model for both J2SE and J2EE. Some of the industry's
best minds will be collaborating to agree upon this standard. By incorporati
ng best-of-breed design concepts, this common POJO persistence model will fu
rther strengthen the Java platform.
We are asking the entire Java technology community to support us and the eff
orts of the JSR-220 Expert Group. We'd like to encourage everyone to contrib
ute to the direction of this persistence work by reviewing the specification
 drafts and sending us your feedback. Your input is crucial to the continued
 success of the Java platform.
Sincerely,
Linda DeMichiel and Craig Russell
Specification Leads, JSR-220 and JSR-243