Community
Participate
Working Groups
assume that i have a project called PersistenceLib, which is not exactly a jpa project, but does contain annotated class for re-use (like super mapped classes and interfaces) now i have the actuall project, which references PersistenceLib and has entities extending them, but the validator doesn't detect them untill i explicitly list them in persistence.xml which is strange and rather inconsistent, becouse it's the validator job's to detect said classes, it simply doesn't scan other projects in the classpath, and it's not like i can define it as a jar file becouse it's not. (not yet)
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?
