There is a difference between a transport error and a SOAP Fault (or at least that's how its meant to be :-) - there may be a bug too). A SOAP Fault is not an error within Synapse and you need to detect it using a XPath. Its possible there is a bug in callout here though. Do you get the same issue if you try a send to the endpoint instead of using callout?
Paul On Wed, Dec 21, 2011 at 3:05 PM, spayasam <[email protected]> wrote: > > Hi All > > I'm trying to run a simple error handler like this > > <sequence name="run_ws" onError="WSFaultHanlder"> > <callout ..> > ... > </callout> > </sequence> > > <sequence name="WSFaultHandler"> > handle errors here ..send email using mailto > </sequence> > > When the callout fails with any error(transport error/soap fault) , the > WSFaultHandler is not getting invoked at all. > I can see that the error is thrown in the synapse log. Am I doing something > wrong? > > Thanks > Shravan > -- > View this message in context: > http://old.nabble.com/Error-Sequences-not-invoked-tp33017415p33017415.html > Sent from the Synapse - User mailing list archive at Nabble.com. > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [email protected] "Oxygenating the Web Service Platform", www.wso2.com
