| Summary: | Static JPQL validation utility | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Neil Hauge <neil.hauge> | ||||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||||
| Status: | NEW --- | QA Contact: | |||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | CC: | douglas.clarke, pascal.filion, peter.krogh, shaun.smith, tom.ware | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Neil Hauge
The utils component seems like a good fit for this functionality. We need to determine the package root for this code. One option would be: org.eclipse.persistence.tools.* since that is what the workbench uses. Another option would be org.eclipse.persistence.utils.* which is more in line with the standard component based naming. It has been suggested by Doug that this contribution be made to the Incubator, where it would be worked on for a period of time before transitioning to Utils. As a result I am changing the component field. Another question that needs to be answered is whether this functionality should be targeted to 2.2 or a future release. Created attachment 181970 [details]
JPQL parser API
The parser has approximately 26 754 lines of code, ~434 classes (including interfaces and enums).
Pascal, please verify that you authored 100% of this code. Thanks. (In reply to comment #3) > Created an attachment (id=181970) [details] > JPQL parser API > > The parser has approximately 26 754 lines of code, ~434 classes (including > interfaces and enums). I confirm that I wrote 100% of the contribution. Created attachment 182476 [details]
Updated source
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |