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 "EclipseLink/Development/JPA 2.0/entitymanager updates"
< EclipseLink | Development | JPA 2.0
(New page: = Updated EntityManager / Query APIs = JPA 2.0 Root | [http://bugs.eclipse.org/248491 Enhancement Request] ==Issue Summary== In JPA 2.0 the specific...) |
|||
| Line 3: | Line 3: | ||
[http://bugs.eclipse.org/248491 Enhancement Request] | [http://bugs.eclipse.org/248491 Enhancement Request] | ||
==Issue Summary== | ==Issue Summary== | ||
| − | In JPA 2.0 the specification extends EntityManager and Query APIs. New APIs have been added for | + | In JPA 2.0 the specification extends EntityManager and Query APIs. New APIs have been added for getting supported properties and getting the owning Entity Manager Factory. |
A new operation 'clear' was also added including a new Cascade Type. Calling clear on an Entity allows the user to remove an Entity and cascaded related entities from the persistence context. Effectively an unregister call. | A new operation 'clear' was also added including a new Cascade Type. Calling clear on an Entity allows the user to remove an Entity and cascaded related entities from the persistence context. Effectively an unregister call. | ||
| + | |||
| + | The new Locking APIs will be covered by the locking functionality feature (http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/pessimistic_locking) | ||
See JPA 2.0 ED section 3.1.1 and 3.2.6 for details. | See JPA 2.0 ED section 3.1.1 and 3.2.6 for details. | ||
==General Solution== | ==General Solution== | ||
| − | + | The implementation of this functionality should be straight forward. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
==Work Required== | ==Work Required== | ||
| − | # Develop | + | # Develop test for testing new non-pessimistic locking APIs |
#: approx 2 days | #: approx 2 days | ||
| − | # Update Processing to | + | # Update Processing to |
| − | #: approx | + | #: approx 3 days - clear(Object entity) |
| − | #: approx | + | #: approx 2 days - remaining APIs |
Revision as of 15:22, 26 September 2008
Contents
Updated EntityManager / Query APIs
JPA 2.0 Root | Enhancement Request
Issue Summary
In JPA 2.0 the specification extends EntityManager and Query APIs. New APIs have been added for getting supported properties and getting the owning Entity Manager Factory.
A new operation 'clear' was also added including a new Cascade Type. Calling clear on an Entity allows the user to remove an Entity and cascaded related entities from the persistence context. Effectively an unregister call.
The new Locking APIs will be covered by the locking functionality feature (http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/pessimistic_locking)
See JPA 2.0 ED section 3.1.1 and 3.2.6 for details.
General Solution
The implementation of this functionality should be straight forward.
Work Required
- Develop test for testing new non-pessimistic locking APIs
- approx 2 days
- Update Processing to
- approx 3 days - clear(Object entity)
- approx 2 days - remaining APIs