Wednesday, July 9, 2008

EclipseLink 1.0 Released

The Eclipse Persistence Services project (EclipseLink) has completed its incubation phase and the 1.0 release is available for download. This release completes the transition of the persistence functionality developed in Oracle TopLink to being fully developed and maintained as an open source project at Eclipse. This also signifies the first release of a project under the recently created top-level Runtime (RT) project at Eclipse.

EclipseLink delivers persistence services for efficiently working with Java and relational, XML, and non-relational data sources. The highlights include:

· Compact: Standard Java distribution is composed of a single implementation jar and utility jars that can be used in any Java SE, IDE, or Java EE hosted environment.

· OSGi: EclipseLink is also available as a set of OSGi bundles. This distribution offers out of the box support for compliant OSGi implementations, as well as Equinox-specific extensions.

· JPA: Superior Java Persistence API 1.0 implementation with many advanced features offering greater flexibility and performance for mapping, caching, querying and transaction processing.

· MOXy: Object-XML binding support with JAXB, offering highly flexible mappings as well as a meet in the middle configuration approach.

· SDO: Service Data Objects 2.1 implementation enabling flexible service integration with dynamic and static models.

· Utils: Migration utilities to assist developers currently using Oracle TopLink or TopLink Essentials in their upgrade to EclipseLink as well as the workbench for compatibility with classic object-relational and object-XML mapping.

A complete index of features and the full user documentation for EclipseLink is available on the Eclipse wiki.

Standards Focused

The mandate of the EclipseLink project is to deliver a set of persistence services that leverage the leading Java standards. In addition, advanced features were added based on user requests but implemented in a way that allows developers to leverage them when needed but not be obstructed by them when they are not needed.

This is particularly true in JPA, where many advanced features are available through JPA persistence unit properties and query hints, in addition to custom annotations and XML. With EclipseLink replacing TopLink Essentials as the reference implementation for JPA 2.0, some of these advanced features will evolve into the specification defined metadata and interfaces. This approach of leading through delivery of advanced functionality, and then contributing back to the standards, is an important aspect of the EclipseLink project.

Growing The Community

The EclipseLink committers understand very well that developing in open source is much more than just providing access to the source code. Building a successful open source project is really about building an active community based on open communication and a transparent development process. We encourage the Java community to try out the 1.0 EclipseLink release and provide feedback. Your contributions and suggestions are valuable to us and will help ensure the project meets your current and future needs.

EclipseLink is currently available directly from the EclipseLink project web site and is also included within the GlassFish and Spring Framework distributions. Going forward, the Oracle TopLink product releases within the Oracle WebLogic Server will also include EclipseLink as its strategic persistence provider.

At present the project has committers from Oracle and Sun but we also have a growing community of users and developers contributing back enhancements. We are eager to expand this community on all fronts to establish the EclipseLink project as the leading persistence solution across Java EE, Java SE, and OSGi.


jawher said...

Great news and great work !
Kudos for the EclipseLink Team :)

Laurent Simon said...

Congratulations, it's good news!

Balakrishna P said...

It is great news. I hope it would be popular opensource ORM framework.

Werner said...

Good to see, that Oracle remains involved and sometimes very active in the Eclipse Community. Despite its less enthusiastic welcome of the Eclipse based project Workshop by BEA. Which competes with its own JDeveloper.

We should therefore see implementations and extensions not just for Eclipse, but most likely at least for JDeveloper, too

mhaller said...

Cool, great news.

Is there a chance to get EclipseLink artifacts into the Maven Central repository please?