Re: IncompatibleClassChangeError

2015-03-25 Thread jburford
I switched to Spring 3.2.6 and it fixed the issue. Thank you for your help! -- View this message in context: http://camel.465427.n5.nabble.com/IncompatibleClassChangeError-tp5764721p5764787.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: IncompatibleClassChangeError

2015-03-24 Thread Willem Jiang
Camel 2.14.x is built with Spring 3.2.x, I think you may need to upgrade the Spring version for it. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On March 25, 201

Re: IncompatibleClassChangeError

2014-06-17 Thread Willem Jiang
Can you recompile your FMSOutboundRoutesTest with Camel 2.13.x? There is the explanation[1] in the stack overflow. [1]http://stackoverflow.com/questions/1980452/what-causes-java-lang-incompatibleclasschangeerror -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.

Re: IncompatibleClassChangeError

2014-06-17 Thread GalinKinlin
I had this error just this morning. Basically, it means you are using an old version of a jar to build some part of your functionality, and a new jar to run it. I was using Spring 3.1.1.RELEASE within my base service, but Camel was using Spring 3.2.8.RELEASE. This is most likely your issue. Check

Re: IncompatibleClassChangeError: Class org.apache.xerces.dom.DeferredElementNSImpl does not implement the requested interface org.w3c.dom.Node / BeanDefinitionParsingException

2011-12-05 Thread bvahdat
Hi, Maybe you want to give it a try to rebuild your application under JDK1.6 and generate your integracja.war from the scratch, as apparently the class org.apache.xerces.dom.DeferredElementNSImpl has been changed in a non-backward compatible way. >From my experience with JBoss, it's also very imp