Hi Claus, I managed to get my case working once I got the fault definitions in my wsdl "correct". I am using the ProxyBuilder and maybe that "inherits" behavior from ProducerTemplate or vice versa, and that was the reason for why that particular exception showed up.
Thanks Lars Skickat från min iPhone 22 apr 2013 kl. 10:45 skrev Claus Ibsen <[email protected]>: > Hi > > CamelExecutionException is usually thrown if you use the producer template > api. > > > On Sun, Apr 21, 2013 at 3:08 PM, helander <[email protected]> wrote: >> I would appreciate some assistance regarding how to handle received Soap >> Faults when using the camel-soap component. >> >> I am using SoapJaxbDataFormat and ServiceInterfaceStrategy. When the >> received response is a Soap:Fault message I get an exception when it is >> unmarshalled, however the exception is not representing the Soap:Fault (as >> per the code generated from the WSDL using cxf tools) but a >> "org.apache.camel.CamelExecutionException". >> I had assumed that the unmarshaller would have produced my service specific >> exception, but maybe I am asking for too much here ;) ? >> >> What would be the appropriate way to make sure an exception representing the >> soap:fault is generated? >> >> Thanks >> Lars >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Handling-of-SOAP-Faults-with-camel-soap-tp5731202.html >> Sent from the Camel - Users mailing list archive at Nabble.com. > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: [email protected] > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen
