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 "JPA2.0AccessAnnotationSupport"
(→Project overview) |
(→Project overview) |
||
Line 21: | Line 21: | ||
Goals: | Goals: | ||
− | * Add JPA Details view | + | * Add a JPA Details view widget 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 | * 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 | * Provide the appropriate defaults and validation for these settings |
Revision as of 10:34, 8 January 2009
Contents
Functional Specification: Dali Support for JPA 2.0 Access annotation
bug 258487 - Access annotation support
Document History
Date | Author | Version Description & Notes |
---|---|---|
1-7-2009 | Karen Butzke | Draft |
Project overview
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
Goals:
- Add a JPA Details view widget 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
Concepts
Present any concepts relevant to the feature.
EclipseLink PrivateOwned annotation documentation
EclipseLink JoinFetch annotation documentation
EclipseLink Mutable annotation documentation
Requirements / Functionality
Private Owned
@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:
- True
- False
Join Fetch
@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)
- Inner
- Outer
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
@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
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.