Interesting…. your camera isn’t properly implementing the soap spec that would require the SOAP fault to be a 500 error code, not a 400.
You can TRY add a contextual property of “org.apache.cxf.transport.no_io_exceptions” to Boolean.TRUE or “true” and seeing if that helps. That would bypass the first place an exception is thrown, but I’m not sure how much further it would go for soap/jaxws. Dan On May 20, 2014, at 7:51 AM, Tobse <[email protected]> wrote: > Hi, > > that didn't work for me. :( > Is there any chance to get the soap message that caused the exception so > that I can log it to my log-file or parse it for more detailed error-codes > in my application? > By the way, I don't have a fix endpoint. > > Kind Regards, > > Tobse > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Re-Exception-in-webservice-communication-How-to-get-additional-informations-tp5744151p5744209.html > Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
