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/Hermes"
< EclipseLink | Development
(→STATUS) |
(→Open Issues) |
||
| Line 22: | Line 22: | ||
=== Open Issues === | === Open Issues === | ||
| + | |||
| + | * package and bundle naming | ||
| + | * number of bundles and dependencies | ||
=== Resolved Issues === | === Resolved Issues === | ||
Latest revision as of 14:23, 23 February 2011
EclipseLink Hermes: JPQL Parser
The EclipseLink Hermes Parser is a set of bundles/fragments and supporting test case projects that deliver:
- a JPQL parser that can be used in IDE integration to validate JPQL queries based on the complete mapping metamodel
- a design time utility that can process queries in source to provide more complete validation of JPQL statements in code
- an alternative JPQL parser to that which is provided by default in the existing EclipseLink bundles
The parser was developed by Oracle and contributed to the EclipseLink project (add CQ/Bug ref).
STATUS
Code checked-in from initial contribution.
TO DO LIST
- Integrate into Build
- Align bundle/project naming
- Ensure bundle/project scope meets consumer's needs
Open Issues
- package and bundle naming
- number of bundles and dependencies