| Summary: | Add Hermes JPQL Parser | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Doug Clarke <douglas.clarke> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | adrian.goerler, douglas.clarke, neil.hauge, pascal.filion, peter.krogh, shaun.smith | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Doug Clarke
Created attachment 188755 [details]
Contribution approved in CQ 4629
Using the approved contribution as is I created two projects. A plugin project for the Hermes parser and a Java project for the supporting test cases. The two projects are visible now at: http://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/trunk/utils/ There are still compile issues with the actual parser. Not sure I got all the necessary package imports in the manifest but it appears there is an issue with the code. All bugs against this parser should be logged against the Utils component with [HERMES] in the subject. Good luck and enjoy. I see much value in having the ability to validate JPQL at build time (as well as at design time). However, from my point of view, the very same parse accessing the very same metadata model should be used at runtime, build time and design time. Otherwise inconsistent checks at runtime and at build-time will be inevitable. Therefore, I second the plan to leverage this new parser at rutime as well. The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |