We encountered some issues on the propagation of partner SOAP-Fault "as is".
We have several project on which it works fine (eg the SOAP faults generated by the partners are propagated "as is") and several other on which this doesn't work. The only difference between the two kinds of projects is the following : on the first, the SOAP-provide is the last service called by the EIP, while on the other projects, their are more stuff to be called. Theoritically, theses steps should not be called, since the the SOAP provide should return a SOAP-Fault.
By the way, the Fault we got in SOAPUI is the following :
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">axis2ns1:Server</faultcode>
<faultstring>A fault occurs during the petals treatment</faultstring>
<detail>
<soapenv:Fault xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
You should find enclosed a service assembly reproducing this issues, along with logs and soapUI project.