Improper Faults in SOAP binding

Question

Maybe someone has seen this and can help with a solution or workaround. We've got a BPEL process that needs to be exposed as a web service to a .NET client. The problem is that only one fault is included in the generated bindings node.
I've defined a BPEL process that throws three test faults. The WSDL has the following portType:
<portType name="TestFaults">
          <operation name="process">
               <input message="client:TestFaultsRequestMessage" />
               <output message="client:TestFaultsResponseMessage"/>
<fault name="faultOne" message="client:FaultOneMessage"/>
<fault name="faultTwo" message="client:FaultTwoMessage"/>
<fault name="faultThree" message="client:FaultThreeMessage"/>
          </operation>
     </portType>
However, when I deploy the process on 10.1.2.0.2 [build #2196 ] we don't get the proper bindings element. It looks like this:
<binding name="TestFaultsBinding" type="tns:TestFaults">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
     <operation name="process">
<soap:operation style="document" soapAction="process"/>
     <input>
<soap:body use="literal"/>
</input>
     <output>
<soap:body use="literal"/>
</output>
     <fault>
<soap:fault name="faultTwo" use="literal" encodingStyle=""/>
</fault>
</operation>
</binding>
The problem is that our .NET client isn't seeing all of the faults, and I assume it is because the different faults aren't included in the SOAP binding??
I've since deployed this same process on 10.1.3. Of course, the new version (which we can't use because we're on AIX) seems to create the binding properly:
<binding name="TestFaultsBinding" type="tns:TestFaults">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<operation name="process">
<soap:operation style="document" soapAction="process" />
<input>
<soap:body use="literal" />
</input>
<output>
<soap:body use="literal" />
</output>
<fault name="faultThree">
<soap:fault name="faultThree" use="literal" encodingStyle="" />
</fault>
<fault name="faultOne">
<soap:fault name="faultOne" use="literal" encodingStyle="" />
</fault>
<fault name="faultTwo">
<soap:fault name="faultTwo" use="literal" encodingStyle="" />
</fault>
</operation>
</binding>

Answer 1

Hi Dieter,
As Bhavesh already mentioned fault messages are used for application errors. The same is described in SAP XI help:
http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm
In case of system error (e.g. field length too long in proxy call or error in XI/PI mapping) there seems to be no standard way of handling it and propagating the response to the consumer of webservice.
Each system error is not recognized by SOAP adapter and SOAP adapter exception is raised.
The only bizzare solution that I can see is developing an adapter module and transport wrong message to standard fault message before delivering it to adapter engine:
http://help.sap.com/saphelp_nw04/helpdata/en/a4/f13341771b4c0de10000000a1550b0/frameset.htm
Kind regards,
Wojciech
btw nice thread