Have an example showing an outbound handler (a cut down version of the SOAP binding), that is invoked to send out a request, but simply attempts to return a fault XML message.

It calls the 'sendFault' method, but it appears that it is being processed as if it was a normal response, as the registered XML to Java Fault object is not being called. This was working in an earlier version of 0.6, but appears to have stopped working in the latest version.

When debugging the test (org.savara.scenario.simulator.switchyard.SwitchyardRoleSimulatorTest) I set a breakpoint on line 295 of ClientProxyBean and found that the exceptionObj was CustomerUnknownType, rather than the expected CustomerUnknownFault.

I then checked TransformSequence.apply and found that the from/to QNames were related to the normal response type (CreditRating) - so I assuming the CustomerUnknownType was simply generated from a jaxb transformation.