2 Replies Latest reply on Aug 22, 2013 11:15 AM by Ashish Rane

    Error Propogation from Split Join back  to Caling Proxy Service

      I am having this problem here where I am not able to access the fault occurred in SJ , in the proxy service from where SJ is invoked . Here is a brief description :

      PS route action calls a SJ . SJ invokes a service and the invoked service throws exception back . I put a scope error handler in "SJ Invoke action" and able to catch the Fault thrown ,by invoked service , and store in a fault variable : say soapFaultVar .I am not doing anything else in SJ exception handler . Infact I don't know what to do .

      soapFaultVar looks something like :

      <ext:soapFault xmlns:ext="http://www.bea.com/bpel/extensions">
      <soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
      <ns2:claimSOAPFault xmlns:ns2="http://ws.claim.zurich.com">
      <message>This functionality is currently not available for this order</message>

      but when check the $fault in the Proxy service it looks like :

      <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
      [{http://schemas.xmlsoap.org/soap/envelope/}Server] 111 &lt;ns2:claimSOAPFault xmlns:ns2="http://ws.claim.zurich.com" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
      &lt;message>This functionality is currently not available for this order&lt;/message>

      Seems although reason in second fault is the string concat of complete first Fault i.e Faultcode , Faultstring and detail . I need the original fault here not the modified one . What can I do here . Anything I could do in SJ Catch block ?? I want soapFaultVar to be in PS , but how to propagate it back to proxy Service ?? Do we have have any predefined variable in SJ (like fault in proxy service) which is returned to PS from SJ in case of error .
      Reply action doesn't seem to work in SJ catch action . Any help greatly appreciated .

      Edited by: 915114 on May 5, 2013 6:53 AM