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? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849502#3849502 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849502 ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
