Marcus wrote: > I'd try using the tomcat classloader if you can. Jboss puts, > afaik, everything into one "universal" classloader. > best, Marcus
Yep, it does, but I do not want to bypass this problem, but instead investigate if there is any way we could change HiveMind to be less strict about the assumption of only one hivemind jar, and thus one hivemind module, loaded by the class loader? Let us, for the moment, put aside all (quite rational) fear of having multiple instances of the same HiveMind classes accessible by the class loader, and focus on the modules instead: is there any way to change RegistryInfrastructureConstructor.java NOT to issue an error when the same module ID is found again, or at least when that duplicate ID is "hivemind"? Hmm, perhaps the current process of using the error handler is the corrrect way; I just wish that Tapestry - in my case - did not use the StrictErrorHandler, since it is, well, too strict for my taste here... I will go and harass the Tapestry guys then ;-) I also wanted to raise awareness of this quite common J2EE configuration (JBoss with the shared class loader set), and its implication for HiveMind-empowered applications: cannot deploy more than one HiveMind-empowered application in such an environment. Thanks, David > > > -----Original Message----- > > From: David Bergman [mailto:[EMAIL PROTECTED] > > Sent: Thursday, August 11, 2005 5:35 AM > > To: [email protected] > > Subject: [hivemind] Multiple HiveMind JARs in JBoss? > > > > > > Hi, > > > > I did not report this as a bug, since I want to understand how > > multiple WARs (each having a separate instance of > > 'hivemind-1.1-beta-2.jar') are supposed to be handled by > the HiveMind > > registry constructor. > > > > I use JBoss 4.0.2 and hivemind-1.1-beta-2 (from Tapestry 4.0) in > > various deployed web applications. The attempt to deploy a second > > HiveMind application yields a "Module hivemind is > duplicated" because > > all instances of the HiveMind JAR has the '<module > id="hivemind">' in > > them, and, of course, the second time, the HiveMind registry > > constructor > > (org.apache.hivemind.impl.RegistryBuilder.constructRegistry) > > will issue an > > ERROR. > > > > My embedded Tomcat 5.5 uses the JBoss class loader, instead of > > Tomcat's own, by the attribute 'UseJBossWebLoader' being > set to 'true' > > in the 'jboss-service.xml' file. I noticed that someone else had a > > similar problem, and this might help them, since they also probably > > used a shared class loader. > > > > The end result being that I cannot have multiple HiveMind > applications > > running in my JBoss server. > > > > The question is: is there any way for the HiveMind registry > > constructor NOT to puke when the module 'hivemind' already exists > > (within the class loader universe...)? > > > > /David > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
