OSB - Fault from downstream service being replaced with generic fault

Question

Hello,
Any "XML Service 1" routes to "Any XML Service 2".
Any XML Service 2 throws this fault:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382612</con:errorCode>
<con:reason>Error preparing message for dispatch</con:reason>
<con:location>
<con:node>Route to Error Queue</con:node>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
Yet in Any Service 1, I only see this fault come back:
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-380000</con:errorCode>
     <con:location>
     <con:node>RouteNode1</con:node>
     <con:path>response-pipeline</con:path>
     </con:location>
     </con:fault>
When I do a Service Callout to Any Service 2 from Any Service 1, I get this:
     <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382502</con:errorCode>
     <con:reason>
     OSB Service Callout action received an error response
     </con:reason>
     <con:details>
     <con1:ErrorResponseDetail      xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config"/>
     </con:details>
     <con:location>
     <con:node>PipelinePairNode1</con:node>
     <con:pipeline>PipelinePairNode1_request</con:pipeline>
     <con:stage>stage1</con:stage>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>
How do I get the original FAULT from Any Service 2?
Thanks!

Answer 1

Just for documentation sake, here is what happens when I kept my services "Any XML" but implemented Anuj's <soap-env:fault> Body and Reply with Success suggestion from the other thread:
Unfortunately it is still not ideal and the behavior widely differs between Service Callout and Route.
Service Callout
<con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382501</con:errorCode>
     <con:reason>
     OSB Service Callout action received an unrecognized response
     </con:reason>
     <con:details>
     <con1:UnrecognizedResponseDetail      xmlns:con1="http://www.bea.com/wli/sb/stages/transform/config">
     <con1:detail>
     &lt;soapenv:Fault xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
&lt;faultcode>500&lt;/faultcode>
&lt;faultstring>Test Error from JJ&lt;/faultstring>
&lt;detail>
&lt;con:fault xmlns:con="http://www.bea.com/wli/sb/context">
&lt;con:errorCode>BEA-382612&lt;/con:errorCode>
&lt;con:reason>Error preparing message for dispatch&lt;/con:reason>
&lt;con:location>
&lt;con:node>Route to Error Queue&lt;/con:node>
&lt;con:path>request-pipeline&lt;/con:path>
&lt;/con:location>
&lt;/con:fault>
&lt;/detail>
&lt;/soapenv:Fault>
     </con1:detail>
     </con1:UnrecognizedResponseDetail>
     </con:details>
     <con:location>
     <con:node>PipelinePairNode1</con:node>
     <con:pipeline>PipelinePairNode1_request</con:pipeline>
     <con:stage>stage1</con:stage>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>
Route
(Success Response)
<soapenv:Body      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
     <soapenv:Fault>
     <faultcode>500</faultcode>
     <faultstring>Test Error from JJ</faultstring>
     <detail>
     <con:fault      xmlns:con="http://www.bea.com/wli/sb/context">
     <con:errorCode>BEA-382612</con:errorCode>
     <con:reason>Error preparing message for dispatch</con:reason>
     <con:location>
     <con:node>Route to Error Queue</con:node>
     <con:path>request-pipeline</con:path>
     </con:location>
     </con:fault>
     </detail>
     </soapenv:Fault>
     </soapenv:Body>