New and Noteworthy

RESTFul Persistence
Java Persistence units can now be exposed over REST using either JSON or XML media. This allows applications to more easily expose their persistence features for direct usage within Thin Server Architecture solutions including HTML5 and mobile clients.	Documentation
Tenant Isolation
Developers can design and deploy applications where their persistent entities manage entities for multiple tenants in the same application with storage in tables per tenant uniquely identified by name or schema. Developers can now alternatively have their applications customize the data source used for different tenant's application instances.	Documentation Examples
NoSQL
Integration NoSQL data stores into an application is becoming a common requirement. Doing this with a common persistence solution is a goal of the EclipseLink project. This release introduces EclipseLink's NoSQL support for MongoDB and Oracle NoSQL.	Documentation Example
JSON
EclipseLink MOXy can now be used for the marshaling and unmarshaling of JSON object. Leveraging the same context and mappings used within the JAXB developers can easily integrate JSON usage to their applications. This is core infrastructure to the JPA-RS feature.	JSON Binding Examples

Enhancements and 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 enhancements.

• Support for JAXB RI Extensions
• Cache invalidation using Oracle QCN/DCN
• MySports Example : Example updated to include @Multitenant(TABLE_PER_TENANT) and the REST interfaces have been replaced with the usage of JPA-RS.
• 2.4.0: All Fixed Bugs and enhancement requests

  Component: Foundation , JPA , MOXy , SDO , DBWS

Known Issues

The following are known issues that have been identified as potentially effecting users of EclipseLink 2.4.

• Bug 370429

  Some methods incorrectly throw a proprietary EclipseLink Exception instead of the equivalent JPA standard exception. Applications will need to catch the proprietary exceptions instead of standard ones. See the bug for more details.

• Bug 408015

  Redeploying a JPA-RS persistence unit will not always update the persistence unit with new mappings. Workarounds are described in the bug.

Standards

EclipseLink remains focused on the delivering support for the latest standards. EclipseLink 2.4 offers certified support for:

• Java Persistence (JPA) 2.0 - JSR 317
• Java Architecture for XML Binding (JAXB) 2.2 - JSR 222
• Service Data Objects (SDO) 2.1.1 - JSR 235

Deprecated Functionality

In EclipseLink 2.4 the following features/API have been deprecated. Please upgrade to the suggested alternatives to avoid issues in the future when these deprecated features/AIP might be removed. release pages .

• Bug 380538 Bug 381207 : Statics previously located on JAXBContextFactory have been deprecated and new values made available on JAXBContextProperties.
• The introduction of the EclipseLink NoSQL release with 2.4 required some EIS API to be moved from the core bundle into the NoSQL bundle. If you have been using these APIs you will need to add the NoSQL bundle to your classpath.
• Bug 399676 : (2.4.2) Deprecation of non-versions REST URIs. JPA-RS accepts request urls with and without version. The URIs without version are deprecated and clients are encourage use versioned ones.

Retention Policy

The EclipseLink 2.4.2 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 page 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.