Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of christian.mueller@gmail.com
 designates 209.85.216.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1352216177986-5722235.post@n5.nabble.com>
References: <1352207386064-5722219.post@n5.nabble.com>
	<71AA771850BD40C68B95D7FE0A30FE54@gmail.com>
	<1352216177986-5722235.post@n5.nabble.com>
Date: Wed, 7 Nov 2012 00:36:51 +0100
Message-ID: 
 <CALvzYd9Nm+SKW-9S2mDuQsNTVnQug6cu-1O6_aJcHzSJna4Mxw@mail.gmail.com>
Subject: Re: CXF SOAP Fault handling
From: =?ISO-8859-1?Q?Christian_M=FCller?= <christian.mueller@gmail.com>
To: users@camel.apache.org
Content-Type: multipart/alternative; boundary=485b397dd4d988932d04cddc13bf

--485b397dd4d988932d04cddc13bf
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Will the "onException" definition work for you? There you can handle the
exception (e.g. execute an alternative route) and abord the routing or
continue the normal routing.

Sent from a mobile device
Am 06.11.2012 16:36 schrieb "vpd" <vishnu_mit2004@yahoo.com>:

> Thanks Willem for your quick response. We tried with no error handler but
> even then routing aborted once SOAP fault is thrown.
>
> I feel that I haven't provided the context clearly. Hence described below=
.
>
>         We have a web service, which can return proper business fault or
> can raise
> an exception as depicted in the below SOAP Responses. In CFX, is their wa=
y
> to differentiate the BUSINESS FAULT from an Exception?
> As I understood, CFX treats all SOAP Fault responses as Exceptions and
> aborts the chain.
>
> Response 1 : Business Fault
> <SOAP-ENV:Envelope xmlns:xs=3D"http://www.w3.org/2001/XMLSchema "
> xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/ "
> xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance ">
>    <SOAP-ENV:Body>
>       <SOAP-ENV:Fault>
>          <faultcode>SOAP-ENV:Server</faultcode>
>          <faultstring>BAD ALBUM</faultstring>
>          <detail>
>             <ns2:FMT2 xmlns:ns2=3D"http://test ">
>                <standard/>
>             </ns2:FMT2>
>          </detail>
>       </SOAP-ENV:Fault>
>    </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> Response 2 : Exception
> <SOAP-ENV:Envelope xmlns:xs=3D"http://www.w3.org/2001/XMLSchema "
> xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/ "
> xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance ">
>    <SOAP-ENV:Body>
>       <SOAP-ENV:Fault>
>          <faultcode>SOAP-ENV:Server</faultcode>
>          <faultstring>javax.ejb.EJBException: ASJ.ejb.005044 (Failed in
> component: sap.com/Test2WSEAR) Exception raised from invocation of public
> test.OrderItunes
> test.ReceiveOrderTest2ImplBean.receiveOrderTest(test.OrderTest) throws
> test.FMT2_Exception,test.FMT1_Exception method on bean instance
> test.ReceiveOrderTest2ImplBean@7846c638  for bean
>
> sap.com/Test2WSEAR*annotation|Test2WS.jar*annotation|ReceiveOrderTest2Imp=
lBean
> in application sap.com/Test2WSEAR.; nested exception is:
> java.lang.RuntimeException: REALLY BAD SINGER!!</faultstring>
>          <detail>
>
> <yq1:com.sap.engine.interfaces.webservices.runtime.RuntimeProcessExceptio=
n
> xmlns:yq1=3D"http://sap-j2ee-engine/client-runtime-error
> ">javax.ejb.EJBException:
>
> =85.</yq1:com.sap.engine.interfaces.webservices.runtime.RuntimeProcessExc=
eption>
>          </detail>
>       </SOAP-ENV:Fault>
>    </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> If I have a route like this
>         <route id=3D=94=94>
>                 <from uri=3D=94=85=94>
>                 <to uri=3D=94cfx:bean:beanName>
>                 <to uri=3D=94component:other=94>
>         </route>
>
> If the first cfx endpoint (cfx:bean:beanName) for invoking the web servic=
e,
> returns a business fault,  I want to extract structure under <detail> and
> pass it on the next processing(component:other).  How it can be achieved?
> Currently, when a SOAP FAULT, occurs, CXF sets an Exception to the Exchan=
ge
> and the camel pipeline will not move to the next processor.
> (Soap11InFaultInterceptor sets the exception to Exchange.)
>
> -- vpd.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/CXF-SOAP-Fault-handling-tp5722219p57222=
35.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

--485b397dd4d988932d04cddc13bf--