Description of problem:
Platform BZ for https://issues.jboss.org/browse/SWITCHYARD-1927 & https://issues.jboss.org/browse/SWITCHYARD-1991

In a Camel route like the following, when an exception is thrown in the normal route and caught in the onException route, the message won't be replied back to the caller of the Camel service and thus eventually timeout exception happens at a service gateway binding:

        onException(Exception.class)
            .handled(true)
            .transform().simple("ERROR: ${exception.message}");

        from("switchyard://ProxyService")
            .handleFault()
            .to("switchyard://ReverseService")
            .transform().simple("OK: ${body}");

Note that this behaviour contradicts the normal behaviour of Camel [1], which is that the following onException clause can send a response back to the caller:

    onException(MyFunctionalException.class)
        .handled(true)
        .transform().constant("Sorry");

[1] https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Fuse/6.0/html/Implementing_Enterprise_Integration_Patterns/files/BasicPrinciples-ExceptionHandling-ExClause.html