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/query definition api"
< EclipseLink | Development | JPA 2.0
(→General Solution) |
(→Issue Summary) |
||
| Line 5: | Line 5: | ||
JPA 2.0 specification has introduced a comprehensive object oriented query definition API which compliments JPQL. | JPA 2.0 specification has introduced a comprehensive object oriented query definition API which compliments JPQL. | ||
| + | This feature is covered in section 5 of the specification. | ||
==General Solution== | ==General Solution== | ||
Revision as of 16:12, 28 October 2008
Query Definition API
JPA 2.0 Root | Enhancement Request
Issue Summary
JPA 2.0 specification has introduced a comprehensive object oriented query definition API which compliments JPQL.
This feature is covered in section 5 of the specification.
General Solution
Should be a simple translation to EclipseLink Queries and Expressions but will be work intensive. Some methods and interfaces can not be completed until the equivalent functionality has been added to EclipseLink
- - see Entity Type Expressions
- - see Collection Parameters for IN
- - see CASE Expressions
Work Required
- Develop model for testing
- approx 4 day
- Update Processing
- approx 13 days - creating query definition implementation.