Julian Gosnell wrote: > 2. Non-compliant - only requests for system classes > are passed upwards.
FWIW, Tomcat4 does the same thing, which means that you have to bundle in jaxp.jar in your webapp, or you're going to get strange class-cast exceptions and class-not-found exceptions. The solution is to bundle all libraries with your app. > This strategy resolves the problems listed against (1) > but causes the isAssignableFrom() test mentioned above > to fail. What appears to happen is that JBoss passes > ClassLoader A to the EJB container which loads class X > then on to Jetty which creates it's WebApp > ClassLoader, B, as a child of A, then asks B to load > class X. B does not delegate to A, but loads class A > for a second time. So you need to put all classes in the EAR scope instead of in the webapp scope to make things work. Right? /Rickard -- Rickard Öberg _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
