SOAP fault propagation for Direct Binding

Hello.We have following set-up
Composite A --- OSB -- Composite B
Composite A exposes HTTP interface (one-way operation) and refers to one-way operation of OSB (over direct binding) which again calls one-way operation of Composite B (again over soa-direct)
Error in composite B is propagated properly to the OSB. I've tested same also with HTTP proxy on OSB, HTTP 500 returned in case of error in Composite B
But Composiet A never raises error to the HTTP service. Thus Consumer is getting HTTP 200, regardless downstream error

try with a non blocking invoke. That will cause a new invoke message to be generated, and a commit of the currently active transaction. So, while the new invoking transaction will be rolled back, a catchable fault will be thrown, and the running tx will commit.
However, if you are not intending to use a transactional system integration, you could go the soap route as well.
your call, my 2cents.

Similar Messages

Error handling for Direct binding

Hi
Anybody handled Direct binding exceptions. I have a requirement if the direct binding service is down I have to catch it and do some action. when I have catch or catchAll not catching it. I am getting rollback fault so my bpel waits continuously in running mode. I have a mediator then bpel. mediator times out but bpel is in running mode.
Thanks
comp

try with a non blocking invoke. That will cause a new invoke message to be generated, and a commit of the currently active transaction. So, while the new invoking transaction will be rolled back, a catchable fault will be thrown, and the running tx will commit.
However, if you are not intending to use a transactional system integration, you could go the soap route as well.
your call, my 2cents.

SOAP Fault Problem for WAS 6.20 System

Hi,
We are exposing some RFC enabled ABAP function modules as web services in a WAS 6.20 system.
We are trying to have all consumers of our web services use the SOAP faults to handle errors.
It works great when we raise exceptions from the function module.
However, we are having an issue when an ABAP dump occurs. It sets the SOAP fault properly,
but the XML return has extra data at the end that is causing our .NET developers problems when
trying to handle the SOAP fault.
Here is the Original(raw) XML:
<?xml version="1.0"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode> SOAP-ENV:Client </faultcode>
<faultstring> Internal Server Error </faultstring>
<detail>
<rfc:Error xmlns:rfc="urn:sap-com:document:sap:soap:functions">
<type> RABAX_STATE </type>
<message> Divide by 0 (type 1). </message>
</rfc:Error>
</detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
sword" value="" size="8"/>
</td>
<tr>
<td> Language:</td>
<td>
<selectname="sap-language" class="pulldown">
<optionvalue="EN"> English</option>
<option value="DE">Deutsch</option>
</select>
</table>
<input type="submit"value="Anmeldung">
</form>
</body>
</html>
The HTML data at the end is causing the problems for our .NET guys.
We have a 6.40 system in development for roll out sometime next year and we don't have this
problem on that system. However, since we are exposing web services on our 6.20 system, we'd
like to get our standards in place now, so that our consumers won't have to change after
the upgrade.
Any information on how to turn off this extra data on a 6.20 system would be appreciated.
Thanks,
Jeff

Hi Andreas,
SOAP 1.2 is not supported, neither in WebAS 6.20 nor in 6.40 as far as I know support is not planed even for next magor release...
The only what I can propose you is to create an OSS and check what shall SAP answer you,
or to downport your applicaiton.
Regards, Angel

A sample web service to return SOAP fault message for application error

Hi,
I need to test behavior of XI, in case of application error (using <detail> tag in soap:fault) from web service in nosoap mode.
If any one is aware of a free web service, which can raise application soap fault message, Kindly provide the details.
Thanks in Advance,
Rahul..

Hi,
What is the URL to which you are posting the SOAP message?
Is it?
http://<host>:<j2ee-port>/XISOAPAdapter/MessageServlet? channel=<party>:<service>:<channel>
If yes, then like mentioned the QOS is picked from the Sender SOAP adapter.
But, if the URL is ,
http://<server>:<ABAP-port>/sap/xi/engine?type=entry&version=3.0&Sender.Service=<YourService>&Interface=<YourNamespace>%5E<YourInterface>
Then you need to give the QOS as <b>,&QualityOfService=ExactlyOnce</b> appended to the above URL.
More, /people/stefan.grube/blog/2006/09/21/using-the-soap-inbound-channel-of-the-integration-engine
Regards
Bhavesh

Sample projects on direct binding in osb 10.3.1

Hi All,
Can anyone suggest me some sample projects in osb 10.3.1 describing direct binding
Thanks in Advance!!

Hi Roshni,
You can find examples for OSB 10.3.1 here, not sure if there's one for direct binding, but may be useful anyway...
http://java.net/projects/oracleservicebus1031/downloads?page=1&theme=java.net
Cheers,
Vlad

Difference between Direct binding , Web service Adapter and HTTP Binding

Can any one help what is the differnce between
*1) Direct binding*
*2) Webservice Adapter*
*3) HTTP Binding*
I am trying to use the above service adapters as references in BPEL.
I had invoked a web service hosted in OSB from BPEL via web service adapter and was successful
On going through few docs came through the other two service adapters but was not able to figure out what exactly is the differnce .
I learnt +"*Direct binding*"+ can be used to call OSB+ . How does it vary from Webservice Adapter+

hi Eric ,
Thanks for clarification ..
OSB does not generate WSDL and web service adapter in BPEL mandates WSDL .
I had to create WSDL separately and then feed into Web service adapter in BPEL to call OSB Proxy service. Though successful , felt its not an better approach.
Please advice is there any way thatWSDL is generated in OSB itself . .if i try to create webservice on Proxy service the wsdl resulted from it has only binding and porty type .
Is it the same case for ++Direct binding++ .I assume it should not be the case

Direct binding faults getting FabricInvocationException

We have two BPEL composites. When one calls the other using SOAP, the caller receives a correct fault, but when I change to direct binding, the fault type is lost and I get a FabricInvocationException instead.
The called composite returns this fault:
<FaultVar>
<part name="fault">
    <PInitWorkflowTransactionFault>
      <nppTxId>
        <nppTransactionId>633919050</nppTransactionId>
        <nppTimestamp>2011/06/13 17:53:14 GMT</nppTimestamp>
        <nppIsRetryFlag>false</nppIsRetryFlag>
      </nppTxId>
      <clientTxId>
        <clientUserId>XYZ</clientUserId>
        <transactionId>100001</transactionId>
        <isRetry>false</isRetry>
      </clientTxId>
      <error>
        <errorClass>1</errorClass>
        <errorCode>10221</errorCode>
        <systemType>WorkflowManager-ProvInit</systemType>
        <errorMessage>Dummy error message</errorMessage>
      </error>
    </PInitWorkflowTransactionFault>
</part>
</FaultVar>In the SOAP version, caller sees this, which is correct:
<bpelFault>
<faultType>1</faultType>
<WFMFault>
    <part name="fault">
      <PInitWorkflowTransactionFault>
        <nppTxId>
          <nppTransactionId>633919050</nppTransactionId>
          <nppTimestamp>2011/06/13 17:53:14 GMT</nppTimestamp>
          <nppIsRetryFlag>false</nppIsRetryFlag>
        </nppTxId>
        <clientTxId>
          <clientUserId>XYZ</clientUserId>
          <transactionId>100001</transactionId>
          <isRetry>false</isRetry>
        </clientTxId>
        <error>
          <errorClass>1</errorClass>
          <errorCode>10221</errorCode>
          <systemType>WorkflowManager-ProvInit</systemType>
          <errorMessage>Dummy error message</errorMessage>
        </error>
      </PInitWorkflowTransactionFault>
    </part>
</WFMFault>
</bpelFault>When I switch to direct binding, using the following reference in the composite.xml, we see the problem.
<reference name="ProvInitializeWorkflowService" wsdlLocation="NPPProvInitializingWorkflow.wsdl">
<interface.wsdl interface="http://www.example.com/network/NPP/ProvInitWF#wsdl.interface(PInitWorkflowPortType)"/>
<binding.direct address="soadirect:/default/ProvInitializingWorkflow!1.0/initprovisioningpayload_client_ep_direct"
                  connection-factory="oracle.soa.api.JNDIDirectConnectionFactory">
    <property name="java.naming.provider.url" type="xs:string" many="false">t3://localhost:8001/default/ProvInitializingWorkflow!1.0/initprovisioningpayload_client_ep_direct</property>
</binding.direct>
</reference>Non-fault replies all work correctly, so we don't have a type mismatch.
Using direct binding, the caller sees this instead:
<bpelFault>
<faultType>0</faultType>
<remoteFault>
    <part name="summary">
      <summary>oracle.fabric.common.FabricInvocationException: oracle.fabric.common.FabricInvocationException:
               oracle.soa.api.invocation.FaultException: {http://www.example.com/network/NPP/ProvInitWF}WFMFault</summary>
    </part>
    <part name="detail">
      <detail>{http://www.example.com/network/NPP/ProvInitWF}WFMFault</detail>
    </part>
    <part name="code">
      <code>null</code>
    </part>
</remoteFault>
</bpelFault>I would really like to use direct binding, but I can't if faults do not work. Help?!
Thanks.

Hello guys,
did you manage to get a patch for your issue?
We have the same one here, a FabricInvocationException at the BPEL layer,
and in the logs
java.lang.ClassCastException: [B cannot be cast to com.bea.wli.sb.transports.client.SOAMessage
     at com.bea.wli.sb.transports.direct.OSBDirectConnection.invoke(Unknown Source)
     at com.bea.wli.sb.transports.direct.OSBDirectConnection.request(Unknown Source)
[ I use SOA Suite 11.1.1.5 ]
thanx
ydes

SOA / SOAP - Direct Binding

Hello,
I have already searched and googled for plenty for online resources about the question, although they haven't really made my concepts clear.
I am following this document - Using the Direct Binding Invocation API
Section : 36.1 Introduction to Direct Binding
for clarifications about Direct-Binding.
Objective : Interaction between OSB and SOA Suite Components(BPEL, Mediator).
Question 1: Why would I use a "direct-binding", instead of a "web/soap binding" ? What are the (dis)advantages ?
I am quoting snippets from the aforementioned document, around which I have some doubts.
[Document] A common way to invoke a composite is to use SOAP over HTTP.
[Question.1] What are other ways of invoking a composite ? I am aware of SOAP over JMS, however, never used it.
[Document] This is enabled by creating a SOAP service for your composite using web service binding. Direct binding enables Java clients to directly invoke composite services, bypassing the intermediate conversion to XML required with web service binding.
[Question.2] What I interpret this is : Composite + WebService Binding = SOAP Service of my Composite. I added a "Direct Binding" to the composite and deployed the service. The deployed concrete "directWsdl" contained 2 auto-generated bindings for SOAP1.1 and SOAP1.2. The Endpoint URL contained "t3" URL. Now the question is, if the aim of direct binding was to avoid to conversion into XML, as with WebService binding, then, why is the deployed directWsdl contains SOAP 1.1 and SOAP1.2 bindings ?
Any pointers to some theoretical books / resources will help !
Thanks !

Direct binding avoids intermediate conversion to XML because an XML Object on client side does not need to be serialized as XML, sent over HTTP(or other transports), deserialized at server and converted to XMLObject again. Client will directly invoke the server side method using RMI and passing the XML object as the input (may be via the direct binding API) this should probably save some processing. But keep in mind that it is not the only reason to use Direct Binding. See the documentation on Direct Binding to identify other benefits or use cases where direct binding may be a good idea.
Oracle SOA Suite Transport (SOA-DIRECT)

Timeout for OSB direct binding

Hi,
I have a OSB proxy invoking Bpel process using direct binding. whenever there is a unexpected error in Bpel the Proxy is not erroring out immediately and is waiting for 2 min before erroring.
When we use SOAP binding we can use read timeout to specify the timeout for response.
How can I do similar stuff using Direct Binding ?
Any suggestions.
Thanks
Sam

Having the same issue. Did you manage to solve this ?

Error "soap fault: No operation available for request" in proxy to soap Scenario

Hi Experts,
Unable to trace the below error when pushing the message from RWB while testing the PROXY to SOAP interface
Delivering the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No operation available for request {http://schemas.xmlsoap.org/soap/envelope/}Envelope.
Thank you very much if any one provided the solution
Regards,
Yugandhar

Hi Yugandhar,
Check the below thread,
Connecting from SAP PI To Salesforce
Regards
RK N.

Error capturing SOAP fault for Sync Messages

Hi
We have a Sync interface which makes a Proxy call from ECC to PI and then PI makes Soap Sync call to Web application. We are having issues when handling Exceptions. Sender is getting misleading errors in response, even though they are application errors the proxy sender is getting error like MappingObjectNotFound.
When debug the PI system, PI is truncating error info when it return the reponse.
Below is the scenario of Synchronous interface:
ECC(Proxy) -> PI(Soap Receiver Adapter) -> MasterDataApp-(Webserver)
Below is the actual response from Webserver (Extracted via TCPGW sniffer):
<?xml version="1.0" encoding="utf-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>*java.rmi.RemoteException: No Messages Found*</faultstring>
<detail>
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
But PI receives this response payload like this :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
<ns1:hostname xmlns:ns1="http://xml.apache.org/axis/">hostname.com</ns1:hostname>
and then Sync Request mesasge fails with below error because of the unexpected response payload as shown above:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID B0CC6B27847A368AA04F4171EF6460F4 Software Component 86524CE0304911DEAE48CC6C83461631</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Also in the response message see this error message:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="http://xml.apache.org/axis/">hostname</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please let me for any clues how to handle this error response.
Thanks,
laxman

Hi Laxman,
SOAP Adapter cannot handle fault responses. I understand your issue. You even want to send the errorneous response from the Webservice as a payload back to the sender. But because of application error from Webservice, you are getting an error in the response message (Mapping Not found). SOAP Adapter cannot handle application error (i.e you will not get the errorneous response in form of payload) . For details please read below:
The receiver adapter expects a SOAP message as response. For synchrnous calls, a successful response should be returned with HTTP 200. In this case, the content of the SOAP body will be returned to the caller as the response payload. When some error occurs, the SOAP message may contain the SOAP fault element. In this case, when the fault detail element is not empty, its content will be returned as the fault payload in an application error message. For others, a system error message will be returned to the caller.
HTTP/1.1 200 OK
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
</SOAP:Body>
</SOAP:Envelope>
will result in an application response message with response payload
<m:GetLastTradePriceResponse xmlns:m="Some-URI">
<Price>34.5</Price>
</m:GetLastTradePriceResponse>
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:MustUnderstand</faultcode>
<faultstring>SOAP Must Understand Error</faultstring>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in a system error message.
HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
<SOAP:Envelope
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<SOAP:Fault>
<faultcode>SOAP:Server</faultcode>
<faultstring>Server Error</faultstring>
<detail>
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope>
will result in an application error message with fault payload
<e:myfaultdetails xmlns:e="Some-URI">
<message>My application didn't work</message>
<errorcode>1001</errorcode>
</e:myfaultdetails>
In order to send the erroneous response as a payload to the sender, you should develop flow in below manner:
ECC(Proxy) -> PI --> ECC(Proxy)
In PI make a SOAP lookup. The response of the SOAP lookup will contain the response given by the WebService (it can be a vaid response or an application error in WebService). Now map this response to the proxy...In this way you can handle the application error msgs from webservice..
I hope this helps you...
Regards,
Rakesh Sharma

SOAP Fault for Application errors

Hi,
I would like to know whether it is OK to raise a SOAP fault for Application or system level exceptions. For example, I'm searching for a user with an ID as request , If the ID is invalid(User is not found) is it OK to raise the SOAP Fault.
Let me know your views regarding the same.

Hi,
With the above explination , please see the below links..
http://help.sap.com/saphelp_nw04/helpdata/en/d0/d4b54020c6792ae10000000a155106/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7521a237-0701-0010-499b-b3285b789c0d
/people/thomas.jung3/blog/2005/01/11/publishing-abap-webservices-to-an-external-uddi-server
/people/sap.user72/blog/2005/11/17/xi-how-to-publish-wsdl-generated-from-xi-to-uddi
Alert rule for SOAP adapter
Monitoring problem in async SOAP receiver adapter
Trapping AF errors using Alert framework in XI 3.0 SP13
Alert Configuration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2f2a9fa2-0a01-0010-32ac-d281db722b86
SOAP Lookup - /people/bhavesh.kantilal/blog/2006/11/20/webservice-calls-from-a-user-defined-function
Regards
Chilla..
<i>Points rewarded if it is useful..</i>

How to raise a soap fault for "business errors"

Hi folks,
I have a scenario.
sync
SOAP<->PI<->RFC
If the update to ECC failed then the RFC response will give back an Error Code in one of the fields, another field will indicate the error description,
I will need to raise a soap fault with this error code and description in the soap fault.
Note , there is only Req and response in the RFC, no fault in the RFC,
Please advice me on this.
Thanks,
Hank

Hi,
I think this could be resolved using multi-mapping.
(RFC)Response - (SOAP) Response
-(SOAP) Fault
In the response mapping, we have RFC response as the source structure , SOAP Response and SOAP Fault as the target structures.DO the validation for ErrorCode and Error Validation in the mapping. Soap Response structure would be generated for succesful RFC response. Soap Fault structure would be generated in case of RFC response containing error code and error message.
Hope it works.
Regards,
Swetha.

OSB: Attach SOAP Header for SOAP Fault

Hi,
Is there a way to return OSB SOAP Fault with custom SOAP Header?
Currently, when SOAP Fault happens, SOAP Header is not returned. I would like to insert some elements in the SOAP header and return when SOAP Fault happens.
Thanks.

Hi Eric,
Thanks for your tips. It was helpful!
I've managed to insert custom SOAP header to a SOAP fault.
In service error handler,
1. Construct custom header and replace header variable content
2. Replace body content with fault variable
3. Reply with failure
Thanks.

Fault propagation from Composite - OSB - Caller

Good morning
I'm trying to implement a OSB as virtualizer from some composite services. For that I have connected the composite via direct binding to the OSB and created a OSB project where I import from URL the composite db WSDL and dependencies and create a Business Service over it. After that I'm creating a proxy service over the created business service automatically.
Everithing works fine in the happy cenario, but the problem is when a business exception configured in the composite occurs.
For example, in this composite I have schematron validation that validate if some fields are correct or not. In case of miss function a ValidationError is thrown.
If I'm calling directly the composite for example from SOAPUi I get the schematron configured fault with:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<env:Fault xmlns:fpre="urn:affinity.xxx.xxx.xxxx.xx">
<faultcode>fpre:internalFault</faultcode>
<faultstring/>
<faultactor/>
<detail>
<ns1:ValidationErrors xmlns:sch="http://www.ascc.net/xml/schematron" xmlns:ns1="http://xmlns.oracle.com/pcbpel/validationservice" xmlns:urn="urn:affinity.xxx.xx.xxxx.xx">
<error>affinity.validation.name.en.mandatory</error>
<error>affinity.validation.name.fr.mandatory</error>
<error>affinity.validation.name.nl.mandatory</error>
<error>affinity.validation.scope.mustBeInternalOrExternal</error>
</ns1:ValidationErrors>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
But when calling via OSB I get:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>BEA-380001: {urn:affinity.xxxxx.xxx.xx}internalFault</faultstring>
*<detail>*
*<con:fault xmlns:con="http://www.bea.com/wli/sb/context">*
*<con:errorCode>BEA-380001</con:errorCode>*
*<con:reason>{urn:affinity.xxxxx.xxx.xx}internalFault</con:reason>*
*<con:location>*
*<con:node>RouteTo_bc-core-affinity-service-bs</con:node>*
*<con:path>response-pipeline</con:path>*
*</con:location>*
*</con:fault>*
*</detail>*
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Can someone help me how can I get the fault propagated to the details instead of the OSB fault ?
Thanks

This is because when OSB encounters a fault, the flow enters the exception pipeline which is composed of stage (or route )error handlers, service error handler and then system error handler. The sequence of flow is :
stage ( or route error handler) --> service error handler --> system error handler.
If some handler is not available, the error is automaticlly propogated to the next handler in the chain. So all errors goes to system error handler unless you specify a reply action within one of the intermediate error handler in which case further flow down the exception pipeline is suspended. System error handler is out of your control and if error reaches here, OSB generates its own fault and replaces the existing one. So if you want to have control make sure the fault is not propogated to the system error handler
Best place to view the exception sequence flow is the trace viewin the test console

SOAP fault propagation for Direct Binding

Similar Messages

Maybe you are looking for