Friends of Eclipse,
Eclipse is an open source community that benefits millions of developers around the world each and every day! During the month of September, we are asking you to give back to our wonderful open source community. All donations will be used to improve Eclipse technology. Your contribution counts!
We thank you for this gesture, and for giving back to our community.
The EclipseLink 2.4 release builds on the increased developer flexibility and multitenant features. EclipseLink now offers support for NoSQL, REST, JSON as well as additional tenant isolation modes for PaaS and SaaS cloud enabled application development.
|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.|
|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.|
|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.|
|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.|
In addition to the features highlighted in the New and Noteworthy section this release also includes a substantial number of bug fixes and enhancements.
The following are known issues that have been identified as potentially effecting users of EclipseLink 2.4.
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.
Redeploying a JPA-RS persistence unit will not always update the persistence unit with new mappings. Workarounds are described in the bug.
EclipseLink remains focused on the delivering support for the latest standards. EclipseLink 2.4 offers certified support for:
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 .
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.
For more information about future planned EclipseLink releases and patch sets please refer to the releases section of the project summary.
Back to the top