0 Replies Latest reply on Sep 24, 2004 5:17 PM by dblock

    Classloader isolation and required jars in deployable

    dblock Newbie

      In my experience, the classloader isolation is working too well. My application will not load once either the jboss-app.xml file is included in the deployed ear, or the jboss-service.xml file is edited to cause all ears to be isolated.

      I'm using 3.2.4, and I'm deploying an ear that contains one jar (EJBs) and one war (Servlets/JSPs). The error message I get initially is:

      Caused by: java.lang.IllegalAccessError: tried to access field org.jnp.interfaces.NamingParser.syntax from class org.jnp.interfaces.NamingContextFactory

      Inclusion of jnpserver.jar leads to other errors including ClassCastExceptions, and JNDI lookups failing. What obvious thing am I missing?