Community
Participate
Working Groups
Build Identifier: 2.3.0.v20110604-r9504 If you add an orm.xml mapping to mark a (for example generated) java class as a mappedsuperclass and the derive from this class and mark it with annotation the EntityManager fails with a null-pointer on schema generation. Described in more detail here: http://www.eclipse.org/forums/index.php?t=rview&goto=726870 Doing everything with annotations works fine. Reproducible: Always Steps to Reproduce: Described here: http://www.eclipse.org/forums/index.php?t=rview&goto=726870 Workaround: As mentioned by James "To workaround the issue try defining both in XML or both in annotations."
This is a duplicate of bug 349906. If possible, please try/use a nightly build of 2.3.1 http://www.eclipse.org/eclipselink/downloads/nightly.php Otherwise, the work around as James suggested is to include the entity in XML as well (just declare it in XML) e.g. <entity class="PersistentLabResultType"/> *** This bug has been marked as a duplicate of bug 349906 ***
(In reply to comment #1) > If possible, please try/use a nightly build of 2.3.1 I can confirm that this problem is solved in the eclipselink-plugins-2.3.1.v20110928-r10176 build.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink