Hivemind is probably using a version of javassist that comes bundled with JBoss, instead of the version deployed with your web application. I can't bash the awful classloader implementation in JBoss bad enough... UnifiedClassloader3, anyone?
Anyways, there's a way out: you need to isolate your web applications from the classloader hell. First, locate the tomcat service in your jboss instalation, and open the META-INF/jboss-service.xml inside the tomcat service folder. Now change the following attributes in this file: Java2ClassLoadingCompliance: false UseJBossWebLoader: false You *may* leave the first attribute as 'true'. It's concerned about how tomcat should deal with the conflicting classloading specifications: Java2 mandates that all classloaders delegates to it's parent before trying to locate the class, while the Servlet specification says that containers should try to locate classes *before* delegating to the parent classloader. The default, true, means that the tomcat will follow the Java2 specification. Setting this to 'false' will make tomcat follow the servlet specification. The second attribute is your heaven: set this to false to tell the tomcat service inside jboss to forget about the hellish JBoss classloader. Now you can live happily everafter. -- Marcus Brito --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
