EclipseLink 2.3.3
The EclipseLink 2.3 release focuses on increased developer flexibility allowing mapped objects to be extensible and multitenant as well as external storage of mappings. These features are intended to help developers address some of the challenges related to developing for cloud architectures and more specifically SaaS solutions.
Release |
Date |
Build |
| EclipseLink 2.3.3 |
July 3, 2012
|
|
| EclipseLink 2.3.2 |
Dec 9 2011
|
2.3.2.v2011125-r10461
|
| EclipseLink 2.3.1 |
Nov 11 2011
|
|
| EclipseLink 2.3.0 |
Jun 22 2011
|
|
New and Noteworthy
Extend Entities |
|
| Developers can make their JPA entities or MOXy JAXB beans extensible so that at runtime a set of additional extended mappings can be used. | |
Support Multiple Tenants |
|
| Developers can design and deploy applications where their persistent entities manage entities for multiple tenants in the same application with storage in a shared table. | |
Externalize Mappings |
|
| Developers can now store mappings using a MetadataSource external to the running application so that mapping overrides and extended mappings can be more dynamically integrated into deployed applications. | |
Multiple Database |
|
| Composite Persistence Units (PU) allows developers to access entities in different data sources by composing their PUs together including support for relationships between entities in different databases. | |
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.
- JPA Stored Procedure and PLSQL Support Enhancements - Documentation
- MOXy support for mapping with predicates
- MOXy support for multiple eclipselink-oxm.xml mapping files
- MOXy support for custom XML name conversions - Documentation
- DBWS from StoredFunction with PL/SQL arguments
- DBWS from overloaded Stored Procedures
- MySports Example : New example showing new @Multitenant and @VirtualAccessMethods features in Java EE web applications using JSF, JAX-RS, EJB and JPA .
- Employee Example : The classic EclipseLink Employee example updated with a JSF front end.
-
2.3.3: All Fixed Bugs and enhancement requests
- Component: Foundation , JPA , MOXy , SDO , DBWS , Utils , Examples , Documentation
Known Issues
The following are known issues that have been identified as potentially effecting users of EclipseLink 2.3.3.
Standards
EclipseLink remains focused on the delivering support for the latest standards. EclipseLink 2.3.3 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.3 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. If you are upgrading from an earlier release please check the applicable release pages .
- Bug 340074: Deprecated use of 'javax.persistence.cacheRetrieveMode' and 'javax.persistence.cacheStoreMode' QueryHints to address JPA 2.0 spec compatibility. The hint names 'javax.persistence.cache.retrieveMode' and 'javax.persistence.cache.storeMode' should now be used.
Retention Policy
The EclipseLink 2.3 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.
