CXF doesn't through the detail exception out by default for the security reason. Aki just contribute a patch[1] last month, if you are using Camel 2.11-SNAPSHOT, you should be able to get this kind exception from the client.
[1]https://issues.apache.org/jira/browse/CAMEL-5755 -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: willemjiang On Tuesday, November 6, 2012 at 11:21 PM, martin11 wrote: > Hi, > > finaly I found source of my original exception. I had garbage in my pom.xml* > <dependency> <groupId>org.apache.cxf</groupId> > <artifactId>cxf-rt-transports-http</artifactId> <version>2.6.2</version> > </dependency> > But my camel version is *2.10.2* which depends on apache-cxf-api wersion > 2.6.3 (btw, it is missing in http://mvnrepository.com/) > > I downloaded camel sources and during debug I found exception: > java.lang.NoClassDefFoundError: > org/apache/cxf/interceptor/StaxInEndingInterceptor > I don`t know why camel override this original exception. Maybe it will be > useful to keep original cause message. > So, I removed unnecessary dependency from pom.xml and everything works as > expected. Second solution is change cxf-rt-transports-http to required > version *2.6.3* instead of 2.6.2. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/CXFRS-Producer-tp5722162p5722234.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com).
