Hi!
I have a number of old EJB 2.1 applications that deploy fine in Glassfish 2 but won't deploy in Glassfish 3.
The CMP/JDO compilation fails because the entity beans are based on an abstract base class defined in a library jar packaged in the EAR. The manifest in the bean jar contains a classpath entry that references the library jar. It seems that for some reason this library jar is not available on classpath when the JDO code generator tries to compile the generated bean implementations.
Is this a bug or is there some way to specify the classpath other than the manifest?
TIA,
Gunnar
[Message sent by forum member 'gugrim']
http://forums.java.net/jive/thread.jspa?messageID=476779