The open source Java persistence platform JPOX has become DataNucleus for its future direction, due to the significant changes in scope of the project since its initiation. The baseline product DataNucleus AccessPlatform, provides persistence to RDBMS, db4o, XML, LDAP and Excel datastores via JDO or JPA APIs.
In this panel, the editors of InfoQ.com (Floyd Marinescu) and ODBMS.org (Roberto V. Zicari) asked a group of leading persistence solution architects their views on the current state of the union in persistence in the Java community.
java.net is hosting an article written by Sharad Acharya titled "Java Persistence Framework: Which, When, and What?" that compares four popular persistence frameworks: CMP Entity EJBs, JPA, Hibernate, and TopLink. Acharya discusses each technology and summarizes his findings in a matrix.
In this talk from last year's QCon London, Linda DeMichiel, who has been leading the EJB spec since the 1.0 days, presents EJB3 with a focus on JPA. The talk covers key aspects of the Java Persistence API and its role in the development of EJB 3.0 apps, including use of the EntityManager API, persistence units and persistence contexts, queries, object/relational mapping, etc.
Recent developer discussion has explored whether JPA has killed the DAO pattern. DAO supporters argue that it isn't going anywhere soon however.
Apache OpenJPA, an open-source implementation of the Java Persistence API (JPA), recently released version 1.0.0. InfoQ spoke with OpenJPA project lead Patrick Linskey to learn more about this release.
Azadeh Ahadian of IBM has published an article introducing JLINQ on IBM's developerWorks site. Despite the name, JLINQ does not have much in common with Microsoft's LINQ, rather it is an Eclipse plugin providing integration with a database and runtime DAO code generation. The plugin is part of IBM's Developer Workbench that is coming with Viper, the next release of DB2.
Apache Geronimo, an open-source Java Enterprise Edition (Java EE) application server, recently released version 2.0.1. InfoQ took the opportunity to learn more about Apache Geronimo and where it fits into the application server space.
OpenJPA is an implementation of the Java Persistence API (JPA) which can be used as a stand-alone POJO persistence layer, or it can be integrated into any EJB3.0 compliant container and many lightweight frameworks. In this interview, Patrick Linskey explains where OpenJPA came from, how it fits into the O/R Mapping space, the JPA specification, and future plans for OpenJPA.
As part of the Eclipse 3.3 (Europa) release two months ago, Version 2.0 of the Eclipse Web Tools Platform (WTP) was released. InfoQ spoke with WTP co-lead Jess Garms to learn more about this release and about WTP in general.
Apache OpenJPA has been gaining momentum in the JEE world, having been adopted by BEA as the EJB3 JPA implementation in WebLogic Server 10 and in the most recent EJB3 Feature Pack for IBM WebSphere Application Server. OpenJPA started its life in BEA's Kodo product, whose code was donated to the ASF in 2006; the project just recently graduated from the Apache Incubator as well.
Oracle is contributing the commercial TopLink ORM open source to Eclipse. Going forward, all production features of TopLink will be available in EclipseLink and Oracle's commercially supported TopLink will only contain an additional thin proprietary integration code layer necessary for some Oracle AppServer and SOA Suite features. Oracle is also becoming an Eclipse Strategic Developer.
OpenXava, the rapid-web application framework, recently released version 2.1. InfoQ sat down with Javier Paniza, project lead for OpenXava to discuss the framework and the new release, which brings JPA support.
In the latest video interview, EJB 3 co-spec lead Mike Keith discusses the current state of EJB 3, including common praises and criticisms that have been received. He also talks about POJO support and how the spec has evolved towards dependency injection.
BEA has released a new tech preview of WebLogic Server 10 that passes the Java EE 5 CTS. WebLogic Server 10 uses the Kodo JPA (based on Apache OpenJPA)and also Spring's Pitchfork project to provide EJB and Java EE 5. WebLogic Server 10 adds side-by-side deployment of multi-version apps, JMS automatic failover, support for document-centric ws-standards, filtering class loaders, and more.