Fault propagation from Composite - OSB - Caller

Question

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

Answer 1

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