Yeah Usually with a WAR all the stuff you put in WEB-INF/lib is isolated. Not sure if you have some common spring JARs in JBoss that is reused.
Maybe there is an option you can tell JBoss if it should use WEB-INF/lib before any common JARs. I know some other JEE servers has such options. On Wed, Nov 6, 2013 at 3:04 PM, rtmacphail <rtmacph...@gmail.com> wrote: > Thanks for the reply. I hadn't noticed the 2.7.0 version number after > CamelNamespaceHandler in the stack trace. My 2.7.0 application and my 2.12.1 > application are both running in the same JBoss container. So I tried > deploying each war separately, and everything works fine. But when both wars > are present, I get the exception. > > The problem, however, doesn't seem to be with the camel version because > originally both applications were 2.7.0 and I got the same exception. I had > upgraded the newer app to use 2.12.1 after the error had first occurred > thinking that there may have been a library conflict with the newer version > of spring (3.2.3). > > Maybe I don't understand the scope of the camel context. I thought each > application would manage it's own context, but is it managed at the > container level? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-2-12-1-Spring-Framework-3-2-3-Jboss-6-0-0-Deployment-Problem-tp5742612p5742713.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
