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]
