EclipseLink/Release/2.1.0

EclipseLink 2.1.0 Release Notes

The EclipseLink 2.1 (Helios) release focuses on providing advanced persistence features for user of relational, XML and Web Services to expose advanced persistence features that naturally extend the industry standards in these spaces.

Release under development see 2.1.0 Plan

Download EclipseLink 2.1.0

• Repositories
  • Helios
  • EclipseLink 2.1
  • Maven
• Complete Install (zip)

New and Noteworthy

• JPA
  • New NetWeaver Server Platform
  • Advanced Querying
    • Casting using TREAT AS
    • Batch reading extended to add IN and EXISTS mode to JOIN
    • FUNC support in criteria and JPQL to invoke database functions
  • Advanced Configuration of JPA extensions using eclipselink-orm.xml files
  • Extended AttributeGroup support for Fetch, Load, Copy & Merge scenarios with partial entities
  • Dynamic Persistence: Bootstrap from eclipselink-orm.xml, API, or native XML

• MOXy
  • JAXB 2.2 Compliance
  • Advanced Configuration using eclipselink-oxm.xml to externalize JAXB and extended mappings
  • Dynamic Persistence from XSD or XML config

• SDO
  • Added server support for WebSphere and JBoss

• DBWS
  • Support DBWSBuilder-generated JAX-WS Provider on JRockit
  • Support for Eclipse WTP Dynamic Web Project structure

Known Issues

OSGi and JPA

In order to use EclipseLink 2.1 OSGi, you must use the org.eclipse.persistence.jpa included with this release. This bundle provides support for Gemini, the reference implementation for the OSGI Java EE integration specification.

Eclipse PDE and MOXy

If a designer creates a PDE project - for a standalone, RCP plugin or headless OSGi app - there is a known issue (298318) that is exposed when the MOXy bundle is included in combination with org.eclipse.core.runtime in the app's list of dependent bundles. When the app is loaded in a Galileo build of the Eclipse IDE, erroneous red-X's will appear with the message: Unsatisfied Version Constraint: 'org.eclipse.core.runtime: 0.0.0'. When the app is loaded in a Helios build, the red-X's do not appear but at runtime the app will not initialize and the error console will report the same Unsatisfied Version Constraint error message.

The workaround for this issue is to remove the org.eclipse.core.runtime bundle from the app's dependency list and instead, convert all use of its APIs to explicit 'Import-Package' entries in the MANIFEST.MF. The plugin-manifest editor's "Dependencies" tab has a section labeled 'Automated Management of Dependencies'. Entering the org.eclipse.core.runtime in this panel and then clicking the 'add dependencies' link will generate all the required package imports.

Resolved Issues

In addition to the features highlighted in the New and Noteworthy section this release also includes a substantial number of bug fixes and enhancement requests.

• All Fixed Bugs and enhancement requests

Property Name Generation from Introspector.decapitalize

The decapitalize method will now leave the property name in uppercase if the first and second characters are uppercase. EclipseLink will use the property name as ID, as detailed in the specification.

Note that this may require a change in some JPQL. For example, if previously you had a method with an annotation such as getCCustomers that would have properties named cCustomers, you will now have Customers.

Retention Policy

The EclipseLink 2.1 (Helios) release will remain available for download from the primary download page until the next release is shipped. At that point it will be moved to the previous releases where it remain for a minimum period of 2 years before becoming available for archival.

Future Releases

For more information about future planned EclipseLink releases and patch sets please refer to the releases section of the project summary.