Related Problem or Business Case

When multiple SoapActions use the same namespace, it is not possible for the framework to distinguish which WebServiceListener the request should go to. In this case, you have to create a routing adapter that accepts all soap requests and then routes them with an XmlSwitchPipe based on SoapAction. This makes scalability very difficult and ugly, and the error handling is also not clean.

Describe the Feature

I would like to be able to specify attribute 'soapAction' on WebServiceListeners and have the framework do routing based on the SoapAction of incoming requests.

Collaboration with External Companies

No, community resolution only

Anything else?

No response