Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Development/JPA 2.0/new collection mappings
< EclipseLink | Development | JPA 2.0
Contents
Element Collections
Summary
JPA 2.0 introduces support for collections of Embeddables and primitives through the @ElementCollection annotation. Support for ElementCollection of primitives will be easily supported through our BasicCollection and BasicMap support and will only require annotation processing updates. Support for lists of Embeddables should be supportable through the AggregateCollectionMapping. Support for Maps of Embeddables will be more difficult and will require completion of the Map Collections support feature.
@OrderBy must also be supported on these collection types.
See section 2.1.5, 9.1.2, 9.1.4, 9.1.7, 9.1.11 and 9.1.35 for details.
Functional Requirements
Design
Work Required
- Develop model for testing
- approx 2 days
- Update Annotation Processing
- approx 2 days - processing @ElementCollection annotation / and XML for primitive
- approx 5 days - processing @ElementCollection annotation / and XML for Embeddables
- approx 5 days - integrating Map collections support for Embeddables
Open Issues
- How does the new JPA @CollectionTable relate to the existing EclipseLink @CollectionTable and what does it mean for users upgrading from one to the other.
- Will EclipseLink support default element collection mappings List<String> or List<MyEmbedable> without requiring @ElementCollection configuration?
- -Supporting defaulting of ElementCollection will break backwards compatibility. In the past this relationship would have been defaulted to a serialized mapping and any models mapped using this default would break upon upgrade to a new EclipseLink version.