WSDLs auto generated via JAX-WS have han empty SOAPAction value. Therefore, message dispatching does not work when using such WSDLS. This issue has been solved in ESB 4.8.0 and later versions. You can do one of the following to overcome this in ESB 4.7.0 and earlier versionsESB 4.6.0. - Append the operation name to the endpoint URL when sending messages to the proxy service (e.g., http://serverName/app/serviceName/operationName).
- Modify the client level code to send the expected SOAPAction value.
- If the WSDL of the back end service has
"" as the SOAPAction value, you should modify the back end service to have a value other than "" for each operation. Note that there is a violation of the service contract by the client if the WSDL of the back end service has a SOAPAction value different to "" when the client sends "" as the SOAPAction value. This should be fixed on client level.
|