How to map a SOAP Fault 1.2 message to SOAP Fault 1.1 in SwitchYard ?

Issue

• Imagine that in a SwitchYard application there is a Service Component named which exposes a SOAP 1.1 compliant interface in form of a SOAP Binding to accept SOAP 1.1 messages and the same service has a Composite Reference that exposes a SOAP 1.2 compliant interface to send out SOAP 1.2 compliant messages to a JAX-WS webservice endpoints.

• In the happy path everything works fine but when the end webservice returns a soapfault (in SOAP 1.2 format) to the SwitchYard service this results in a SOAP Fault from the same service which looks like this.

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP-ENV:Header xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"/>
   <soap:Body>
      <SOAP-ENV:Fault xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
         <faultcode>SOAP-ENV:Server</faultcode>
         <faultstring>SWITCHYARD035453: Invalid response SOAPMessage construction.  The associated SwitchYard Exchange is in a FAULT state, but the SOAPMessage is not a Fault message.  The MessageComposer implementation in use ("org.switchyard.component.soap.composer.SOAPMessageComposer") must generate the SOAPMessage instance properly as a Fault message.</faultstring>
      </SOAP-ENV:Fault>
   </soap:Body>
</soap:Envelope>

This is how the server.log reports this issue.

SWITCHYARD035453: Invalid response SOAPMessage construction.  The associated SwitchYard Exchange is in a FAULT state, but the SOAPMessage is not a Fault message.  The MessageComposer implementation in use ("org.switchyard.component.soap.composer.SOAPMessageComposer") must generate the SOAPMessage instance properly as a Fault message

• How to resolve this kind of issue?