[switchyard-issues] [JBoss JIRA] (SWITCHYARD-761) SOAP Gateway does not use soapAction definition from WSDL binding

Keith Babo created SWITCHYARD-761: ------------------------------------- Summary: SOAP Gateway does not use soapAction definition from WSDL binding Key: SWITCHYARD-761 URL: https://issues.jboss.org/browse/SWITCHYARD-761 Project: SwitchYard Issue Type: Bug Components: component-soap Affects Versions: 0.4 Reporter: Keith Babo Fix For: 0.5 Given a WSDL with the following binding: {code} <wsdl:binding name="SomeBinding" type="tns:SomePortType"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsdl:operation name="SomeOperation"> <soap:operation soapAction="/My/SoapAction" soapActionRequired="true" style="document"/> {code} The SOAP gateway is not adding a soapAction header to the outbound message. This is due to the fact that the BindingProvider defaults to *not* adding a soapAction to the message. We need to change the default to add soapAction with the appropriate value from the WSDL. More info on the appropriate properties in JAX-WS: http://docs.oracle.com/javase/6/docs/api/javax/xml/ws/BindingProvider.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira