Originally posted by Jeff Shelley:
actually, man, it happens to me when there's only one deployed. So I don't know. This is getting fun, though.
Originally posted by Jeff Shelley:
I had not configured it. That's giving me some error from some InitFilter.
org.picocontainer.defaults.DuplicateComponentKeyRegistrationException:
Key class org.snipsnap.container.MessageLogService duplicated
at org.picocontainer.defaults.DefaultPicoContainer.registerComponent(DefaultPicoContainer.java:80)
at org.picocontainer.defaults.DefaultPicoContainer.registerComponentImplementation(DefaultPicoContainer
So I'll have to play with that for a while.
[ June 24, 2004: Message edited by: Jeff Shelley ]
Originally posted by Jeff Shelley:
ok. I was able to deploy both of them.
My jboss-service.xml doesn't have any of those
Java2ClassLoadingCompliance or UseJBossWebLoader settings anywhere.
I didn't need to mess with war scoped loading either.
but then again. I wasn't able to find version 0.5.1a, so I used 0.5.2a.
Do you think your distribution could have become corrupted during your download?
Originally posted by Jeff Shelley:
What Request URI caused your error? I had always thought that the jars in lib directories in web archives were treated differently than jars in ears.
Originally posted by Jeff Shelley:
I'm gonna try that out. Is there anything you could send me to help out? like are you using classes, jars, jsp's?
When things "blow up" is it because they affected each other, or they blew up individually?
Originally posted by Jeff Shelley:
Also, in the mean time, would putting your xml jar in the main deployer (the deploy directory) fix that?