The user is proxying requests to SAP and requests an enhancement that will save significant time and cost. As it is described to us:

Use case is SOAP-Camel-Proxy for one-way Webservice calls that are "buffered" in a JMS queue. This pattern is used a lot when we integrate between JavaEE and SAP-ERP using asynchronous request/reply patterns impemented with SOAP Webservices ( SAP-ERP cannot be a JMS client without buying SAP's ESB).

A Java application calls a one-way Webservice to FUSE that queues the call:
(SY-app: SOAP Service Binding to Camel-Component to JCA-ActiveMQ JMS Reference Binding).

FUSE then takes the message from the queue and sends it to SAP using WS-ReliableMessaging:
(SY-app: JCA-ActiveMQ JMS Service Binding to Camel-Component to Camel-CXF Reference Binding).

For this second portion of the route it would be nice if the Camel-Reference Binding could use the dispatch-mode, because the message body that comes from the queue should just be "forwarded" to the SOAPService of SAP.

At the same time the dispatch-mode should consider the (WS-RM and Security) Policies defined in the WSDL (but when configuring the WSDL the dispatch-mode is not used at the moment).

It would also be nice for this part of the route if Switchyard wouldn't force use of an OperationSelector on the JMS Service Binding because the reference Binding just sends the message as is.