Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLinkNewAttributeMappings"
(→Basic Map) |
(→Basic Map) |
||
| Line 54: | Line 54: | ||
* Default Key Column name is <field/property-name>_KEY | * Default Key Column name is <field/property-name>_KEY | ||
* Default [[Using_EclipseLink_JPA_Extensions_(ELUG)#How_to_Use_the_.40CollectionTable_Annotation|@CollectionTable]] name is <Entity-name>_<field/property-name> | * Default [[Using_EclipseLink_JPA_Extensions_(ELUG)#How_to_Use_the_.40CollectionTable_Annotation|@CollectionTable]] name is <Entity-name>_<field/property-name> | ||
| + | |||
| + | From the EclipseLink docs, we can create validation for this. Need to verify that I understand the second statement: | ||
| + | Note: If you specify @BasicMap on an attribute of type Collection, EclipseLink will throw an exception: the type must be Map. If you specify the fetch type as LAZY, Map implementation classes are also not valid. | ||
| + | |||
[[Image: BasicMapMapping.jpg]] | [[Image: BasicMapMapping.jpg]] | ||
Revision as of 10:14, 27 June 2008
Contents
Functional Specification: Dali Support for New EclipseLink Attribute Mappings
bug 238460 - basic collection mapping support
bug 238462 - basic map mapping support
Document History
| Date | Author | Version Description & Notes |
|---|---|---|
| 6-25-2008 | Karen Butzke | Draft |
Project overview
This feature is about adding the new attribute level mappings annotations supported by the EclipseLink JPA extension.
Goals:
- Add JPA Details view widgets for the BasicCollection and BasicMap annotations
- Add JPA Details view widgets for eclipselink-orm.xml basic-collection and basic-map elements
- Provide the appropriate defaults and validation for these mappings
Concepts
Present any concepts relevant to the feature.
EclipseLink BasicCollection annotation documentation
EclipseLink BasicMap annotation documentation
EclipseLink CollectionTable annotation documentation
Requirements / Functionality
Basic Collection
- Supported in Entity, MappedSuperclass, and Embeddable classes.
- Default fetch type is Lazy
- Default Value Column name is <field/property-name>
- Default @CollectionTable name is <Entity-name>_<field/property-name>
Basic Map
- Supported in Entity, MappedSuperclass, and Embeddable classes.
- Default fetch type is Lazy
- Default Value Column name is <field/property-name>
- Default Key Column name is <field/property-name>_KEY
- Default @CollectionTable name is <Entity-name>_<field/property-name>
From the EclipseLink docs, we can create validation for this. Need to verify that I understand the second statement: Note: If you specify @BasicMap on an attribute of type Collection, EclipseLink will throw an exception: the type must be Map. If you specify the fetch type as LAZY, Map implementation classes are also not valid.
API
Issues
This section lists the open issues that are still pending that must be decided prior to fully implementing this project's requirements.
| Issue # | Owner | Description / Notes | Decision |
|---|---|---|---|
Future Considerations
During the research for this project the following items were identified as out of scope but are captured here as potential future enhancements. If agreed upon during the review process these should be logged in the bug system.