Thanks everybody, My solution was to simply remove the jboss-aop.deployer (containg Javassist 3.0) from the JBoss 4.0.1 default deploy folder.
To me somewhat surprising it did not solve my problems to simply isolate my WAR using the flags Brito kindly told me about. It simpy caused more problems finding other classes and resources. To have a less complex WAR to work with (my own contains lots of Struts/Hibernate stuff) I created a simple HiveMindHelloWorldServlet ANT project, would that app be meaningful at the Wiki or would it just overlap and confuse others? regards, Jens -----Original Message----- From: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 23, 2005 2:12 PM To: [email protected]; Marcus Brito Subject: Re: ApplicationRuntimeException when constructing HiveMind registry in JBoss Looks like conflicting versions of Javassist. On Tue, 22 Mar 2005 18:20:39 -0300, Marcus Brito <[EMAIL PROTECTED]> wrote: > 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] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
