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.
The Hibernate team has released Hibernate 3.2 GA. This release is ready for production use and includes final releases of the Java Persistence provider, Hibernate Annotations and Hibernate EntityManager. The Hibernate Java Persistence provider has been certified with the Sun TCK.
BEA has announced the completion and delivery of WebLogic Platform 9.2 (Server, Portal, and Integration) that are designed to provide a unified foundation for BEA's SOA 360 platform. Kodo 4.1, Workshop, and Workshop Studio also had new releases. InfoQ summarized the new features in WL Server and Portal.
The EasyBeans EJB3 container project recently announced support for deploying the container as a set of OSGi modules. InfoQ sat down with Florent Benoit of Bull R&D to discuss this new feature as well as how EasyBeans compares to other EJB3 implementations such as JBoss and Gernonimo.
Spring 2.0 final is set to come out on September 26th - a few months after the original launch dates. InfoQ spoke to the Spring team to find out what's been going on. Spring has been updated with JPA final spec support, asychronous JMS, the new JSP form tag library, and a collaboration with IBM, BEA, and Oracle to bring OSGi support to Spring.
devx is hosting an article comparing Spring 2 and EJB 3 focusing on support for persistence, transaction management, and statefulness, concluding that support is mostly the same with but with EJB being slightly better at handling state.
BEA has finished the last set of OpenJPA code drops to the Apache Incubator. OpenJPA will be an enterprise grade JPA implementation suitable for production use. It will also form the basis for BEA's commercial Kodo 4.1 and WebLogic's JPA support.
The Java BluePrints Catalog available on Java.net has been updated with new writeups on JSF, AJAX, and JavaEE 5 Persistence.
Artima has interviewed EJB 3 spec lead Linda DeMichiel on how EJB was refactored for simplicty between EJB 2 and EJB 3, including three separate spec documents, simplifying EJB interfaces, annotations and when to use them, and dependency injection.