Functional Specification: Dali Support for JPA 2.0 Access annotation
bug 258487 - Access annotation support
|Date||Author||Version Description & Notes|
This feature is about adding the new JPA 2.0 Access annotation. This will only be added to the EclipseLink platform and is supported in EclipseLink 1.1
- Add JPA Details view widgets for changing the access type of java Entities, MappedSuperclasses, and Embeddables
- Add JPA structure view support for adding mixed access mappings and changing existing mapping to the opposite access
- 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 a combo box:
- Default (Inner)
A checkbox is used to enabled Join Fetch, if you check it the JoinFetch annotation is added and the combo box is enabled and displays Default(inner).
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. 241265
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.