The tooling is generating warnings saying a component is calling out to a service with more than one operation, when only one operation exists on the service interface. See either the switchyard-demo-multiApp-order-consumer or switchyard-ear-deployment-order-consumer quickstarts for an example of the error.

The camel-soap-proxy provides an interesting case where this is more than one operation available, but I'm assuming the operation name gets passed through from the composite service (which inherits the interface). That said, when I tried adding ?operationName=reverse to the route, I got an error saying the operation did not exist.