This is the expected behavior with GlassFish 3.*. The classes inside war
file should not be visible to the ejb jar (Java EE 6 has enforced the
rules of jar visibility which is reflected in the GlassFish 3.*
implementation). It worked in v2.* probably because the ejb jar and war
were loaded by the same classloader. To make this work for GlassFish
3.*, you probably have to repackage the application in a portable way,
move the class that need to be visible to the both war and ejb jar to an
ear library jar.
- Hong
On 4/3/2012 11:30 AM, forums_at_java.net wrote:
> Thanks for the reply. This is how I have packaged: MyEar.ear --
> META-INF --
> application.xml -- lib -- myEar.ejb.jar -- -- myEar.war -- META-INF --
> WEB-INF -- classes -- web.xml -- glassfish-web.xml While deploying the
> ejb
> classes packaged under myEar.ejb.jar is trying to access the classes
> in the
> myEar.war which is throwing the "class Not Found exception"
>
> --
>
> [Message sent by forum member 'paddy_g']
>
> View Post: http://forums.java.net/node/884764
>
>