Hello, Stephan.
Which JAR contains the class in the exception?
You could try deploying the EAR using the asadmin command line utility and
specifying
--compatibility=v2
This might help because the Java EE 6 spec is much stricter than Java EE 5
about which JARs in an EAR each module is allowed to see. GlassFish 3
implements Java EE 6 so it enforces the tighter restrictions by default.
Normally an app client will be able to access any JAR listed in the app
client JAR's manifest Class-Path plus any JARs in the EAR's library directory
(/lib by default).
The added option uses the older behavior that does not comply with the more
restrictive rules in Java EE 6. Naturally, if this proves to be the problem
then I'd suggest that you revise your application so it complies with these
new Java EE 6 rules, primarily so you won't need to remember to deploy it
with the added option. (By the way, in v2 an app client was allowed to
access any EJB JAR as well as any JAR at the top level of the EAR.)
Hope that helps.
- Tim
--
[Message sent by forum member 'tjquinn']
View Post: http://forums.java.net/node/715589