BEA Finishes Moving OpenJPA Code to the Apache Incubator

Posted by Scott Delap on Jul 25, 2006

Sections

Operations & Infrastructure,

Architecture & Design,

Development

Topics

Open JPA ,

JPA ,

Java EE ,

Java ,

Languages ,

Data Access ,

Database ,

Programming ,

BEA

Share |

RELATED Research

OpenJPA will be an enterprise grade JPA implementaiton suitable for production use. In addition to the JPA API it will also extend the JPA with features from Kodo including custom lock groups, dynamic fetch group configuration, custom mapping capabilities, Kodo save point capabilities, DB level save points, programmatic access to introspection of named queries, caching and even Kodo's built-in distributed cache implementation with hooks to plug in Tangosol's Coherence.

Some Kodo IP will be reserved for use in WebLogic Server and the commercial Kodo product, such as management and monitoring tools, more aggressive caching and scalability algorithms, deploy time and runtime features.

Neelan Choksi provides an update on the Kodo to OpenJPA transition on his blog:

Where this really gets interesting is also one of the reasons that we took a while to get the code out there. We had to refactor some of Kodo code so that the next release of Kodo will basically sit on top of OpenJPA. Not wanting to maintain separate code bases, BEA decided that OpenJPA will be the basis for all future versions of Kodo. This is pretty major news because the next release of Kodo will also be included as part of the next major release of WebLogic Server (code named "Dante") as its O/R mapping engine. This should give customers a comfort level and a sense of confidence in this open source project that it will be around for a while and it has commitment from BEA as well as a number of our friends in other organizations. I am sure you will be seeing announcements in the near future about the support that the community will be throwing behind OpenJPA and am truly excited about this being a cross-community project and not just a BEA project.

By providing OpenJPA under the business friendly Apache Software License, OpenJPA may present a viable alternative to Hibernate (earlier InfoQ article with a lively discussion).

RelatedVendorContent

Introducing SQLFire: a memory-optimized, high performance SQL database

Tutorial: Integrating SQLFire with tc Server and Spring Data

The WebSphere Liberty Profile for Developers: An Introduction

Introduction to WebSphere Liberty Profile

Big Data, Cloud & Mobile: Navigate the New Development Reality with Resources from IBM

Related Sponsor

VMware vFabric SQLFire - Test drive the data management system with memory speed, horizontal scalability and a familiar SQL interface

1. Back to top

   Status?

   by Ashley Aitken

   A couple of question:
   
   1. Can OpenJPA be used (successfully) now? If it compiles ... is there a Jar (or two or three)? What about documentation (I assume the Kodo docs)?
   
   2. Are the differences between OpenJPA and the commercial Kodo offering clearly defined (ie more than above) somewhere? Is so, where?
   
   Thanks,
   Ashley Aitken.
   Perth, Western Australia.

   Reply

2. Back to top

   Re: Status?

   by karan malhi

   You could download using a subversion client and compile it using Maven2. I think the openjpa website says that it is going to post the javadocs pretty soon

   Reply