I deployed an .ear to GlassFish with the following structure: (Result from: jar tf MyProject.ear)
META-INF/ META-INF/MANIFEST.MF lib/ lib/openjpa-all-2.1.1.jar lib/MyProject-pojo.jar MyProject-ejb.jar MyProject-ws.war Both MyProject-ejb.jar and MyProject-ws.war have a MANIFEST.MF file with a "Class-Path: lib/MyProject-pojo.jar" in them. However, when I deploy this .ear archive to GlassFish (3.1.1), I receive an error: [...] at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransformer.java:144) ... 77 more Caused by: java.lang.ClassNotFoundException: my.package.MyClass [...] Apart from the error message, which I'm still investigating, it looks as if GlassFish indeed automatically tries to enhance my entities. Can I safely ignore vague warnings on the web NOT to thrust this "auto enhance feature", or is there a particular reason I should still enhance the entities myself at build time (when deploying to GF3)? -- View this message in context: http://openjpa.208410.n2.nabble.com/Enhancement-necessary-in-GlassFish-3-tp6778727p6778727.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
