Notice: This Wiki is now read only and edits are no longer 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/properties processing"
< EclipseLink | Development | JPA 2.0
(New page: __NOTOC__ = JPA 2.0: Property Processing = JPA 2.0 Root | {{bug|249023}} {|{{BMTableStyle}} |-{{BMTHStyle}} ! Date ! Committer(s) ! Description |- ...) |
(→Summary) |
||
| Line 15: | Line 15: | ||
== Summary== | == Summary== | ||
| + | The JPA 2.0 Specification provides functionality to set properties on the EntityManager at runtime. Before that feature can be completed we must define what properties can be set on the Entity Manager and when. This will allow use to clearly communicate to our customers how and when certain configurations can be applied. | ||
| + | We must also update our property processing to ensure properties can be processed on a per property basis and that the property processing functionality is complete and available. | ||
=== Work Estimate === | === Work Estimate === | ||
| + | * Define all properties and when they apply | ||
| + | ** 1 day | ||
| + | * Update property processing to account for lifecycle and validation | ||
| + | ** 4 days | ||
| + | * write tests to verify validation and lifecycle | ||
| + | ** 2 days | ||
== Functional Requirements == | == Functional Requirements == | ||
Revision as of 15:32, 24 March 2009
JPA 2.0: Property Processing
| Date | Committer(s) | Description |
|---|---|---|
| March 24, 2009 | gyorke | Initial feature template |
Summary
The JPA 2.0 Specification provides functionality to set properties on the EntityManager at runtime. Before that feature can be completed we must define what properties can be set on the Entity Manager and when. This will allow use to clearly communicate to our customers how and when certain configurations can be applied. We must also update our property processing to ensure properties can be processed on a per property basis and that the property processing functionality is complete and available.
Work Estimate
- Define all properties and when they apply
- 1 day
- Update property processing to account for lifecycle and validation
- 4 days
- write tests to verify validation and lifecycle
- 2 days
Functional Requirements
Existing Feature Impact
| Feature | Supported | Notes |
|---|