ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From George <george.n...@gmx.net>
Subject Capture Soap Fault in Invoke
Date Thu, 11 Aug 2011 11:04:58 GMT
Hi all,

I'm trying to capture a custom Soap Fault returned from an invoke activity.

I have successfully capture the exceptions lauched when the remote service is unavailable
by using <ext:failureHandling>. However now the problem is different.

My remote service is a function like this:
public void sendMyServiceException(int i) throws MyServiceException

When I call it using SoapUI I get the exception soap xml code:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
          <MyServiceException xsi:type="ax21:MyServiceException" 

However in my BPEL process I'm not able to see it. The BPEL code for this part is:
<bpel:invoke name="InvokeException" partnerLink="ServiceEmulatorPL" 

  <ext:failureHandling xmlns:ext="http://ode.apache.org/activityRecovery">

      <!-- Assign data to variable output from invoke PingPongPLResponse -->
      <bpel:assign validate="no" name="AssignIteratorInCaseOfError">

I use catchAll to capture everything but I don't get any error, that is, the variable $iterator
is not modified and still stores the same value as the one assigned before. I have tried with
faultOnFailure set to true and false and no difference.

When analizing the logs it seems that after ODE engine makes the call to the remote WS it
directly returns without displaying anything on the log about the soap fault. When using a
IN/OUT call I get both the request and response on a correct execution displayed on the log,
but in this case only with IN and Exception, I only get the request.

Any help. I would really appreaciate it.


View raw message