Functional Specification: Dali Support for EclipseLink Attribute Mapping Options
bug 238441 - private owned support
bug 238455 - join fetch support
bug 238458 - mutable support
|Date||Author||Version Description & Notes|
This feature is about adding the new attribute level annotations supported by the EclipseLink JPA extension.
- Add JPA Details view widgets for the PrivateOwned, JoinFetch, and Mutable annotations
- Add JPA Details view widgets for eclipselink-orm.xml private-owned, join-fetch, mutable elements
- Provide the appropriate defaults and validation for these settings
Present any concepts relevant to the feature.
Requirements / Functionality
@PrivateOwned annotation is supported on OneToOne, OneToMany and VariableOneToOne mappings. The corresponding element in the eclipselink-orm.xml is private-owned.
Private owned options, to be displayed as a check box:
@JoinFetch annotation is supported on OneToOne, OneToMany, ManyToOne, ManyToMany, BasicCollection, and BasicMap mappings. The corresponding element in the eclipselink-orm.xml is join-fetch.
Join Fetch options, to be displayed as combo box:
- Default (Inner)
How do we handle no @JoinFetch annotation meaning no default? The Default of Inner is only if the @JoinFetch annotation exists and no JoinFetchType is specified. Should we use a check box and a combo box? We also have the same problem with the existing Enumerated widget.
Private owned and join fetch widgets on a OneToOne
@Mutable annotation is supported on Id, Basic, Version, and Transformation mappings. The corresponding element in the eclipselink-orm.xml is mutable.
If attribute type is Serializable then mutable defaults to true, otherwise it defaults to false. If no Mutable annotation is specified and the type is a Date or Calendar the default is taken from the persistence unit property eclipselink.temporal.mutable 228042. Where should this setting go in the EclipseLink persistence.xml editor?
Possibly put a hyperlink from Mutable to the global setting in the persistence.xml editor, could do this for other settings as well.
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|
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.