Welcome!

Eclipse Authors: David Smith, RealWire News Distribution, CJ Fearnley

Related Topics: Java, Eclipse

Java: Article

A Plea for POJO (Plain Old Java Object) Persistence Model

Spec leads of JSR-220 and JSR-243 hope to reconcile Java's conflicting persistence models

The following is the text of an Open Letter written by Linda DeMichiel and Craig Russell, the two specification leads for JSR-220 and JSR-243:

"A Letter to the Java Technology Community

For years, the Enterprise JavaBeans (EJB) and Java Data Objects (JDO) specifications have evolved independently as they addressed different sets of requirements. The core of both specifications, however, includes persistence technology. Even to this day, the data persistence models in EJB and JDO differ significantly. This divergence has caused confusion and debates among Java developers, and is not in the best interest of the Java community. 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 Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community. This effort will strengthen community solidarity.

Starting this reconciliation effort now is very timely given that both the EJB and JDO specifications are going through significant revisions. As specification leads for EJB 3.0 (JSR-220) and JDO 2.0 (JSR-243), we have jointly created the following plan to move this community effort forward:

This is a community effort. We are expanding the JSR-220 Expert Group to include 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 current JSR-220 specification lead will remain unchanged.

The work to define a single POJO persistence model for the Java community will 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 developers 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 specification, Reference Implementation, and Technology Compatibility Kit, usable 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 those with a preference for JDO query style can leverage the new common persistence API. The current JSR-243 specification lead will remain unchanged.

We believe this is a unique opportunity for the Java community to create a common POJO persistence model for both J2SE and J2EE. Some of the industry's best minds will be collaborating to agree upon this standard. By incorporating best-of-breed design concepts, this common POJO persistence model will further strengthen the Java platform.

We are asking the entire Java technology community to support us and the efforts of the JSR-220 Expert Group. We'd like to encourage everyone to contribute 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"

More Stories By Java News Desk

JDJ News Desk monitors the world of Java to present IT professionals with updates on technology advances, business trends, new products and standards in the Java and i-technology space.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.