| Summary: | JPA validator does not detected classes in other projects in the class path | ||
|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | elhanan Maayan <elh.mailgate> |
| Component: | JPA | Assignee: | Brian Vosburgh <brian.vosburgh> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | brian.vosburgh, neil.hauge |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
elhanan Maayan
This is a current limitation of our binary class support. I can't find an existing bug regarding this limitation, so will use this as tracking bug for this functionality. Targeting to Juno release. It's not clear what you are expecting. Currently, Dali will validate either: - the classes it discovers via the persistence.xml file or - the classes in the project that are annotated (if the JPA project property "Discover annotated classes automatically" is activated) Obviously, a class in another project can be referenced by a class in the current project. If the referenced class is listed in the persistence.xml file, Dali will process its annotations etc. If the referenced class is not listed, Dali will ignore the annotations. This is a feature. :-) You may not want Dali to process the annotations in the other project, and if Dali did there would be no way to ignore and/or override the annotations. Could you give an example of the classes you are talking about and the sort of validation you expect? |