SwitchYard
  1. SwitchYard
  2. SWITCHYARD-761

SOAP Gateway does not use soapAction definition from WSDL binding

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 0.4
    • Fix Version/s: 0.5
    • Component/s: component-soap
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      Given a WSDL with the following binding:

      <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"/>
      

      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

        Activity

        Hide
        Magesh Bojan
        added a comment -

        Both properties soapActionRequired and style are SOAP 1.2 constructs. Since we added support for this recently, turning this issue into an enhancement.

        http://schemas.xmlsoap.org/wsdl/soap12/soap12WSDL.htm

        Show
        Magesh Bojan
        added a comment - Both properties soapActionRequired and style are SOAP 1.2 constructs. Since we added support for this recently , turning this issue into an enhancement. http://schemas.xmlsoap.org/wsdl/soap12/soap12WSDL.htm
        Hide
        Keith Babo
        added a comment -

        Is this issue really specific to SOAP 1.2? So I could use the soapAction attribute alone in a WSDL for a SOAP 1.1 binding and it would work?

        Show
        Keith Babo
        added a comment - Is this issue really specific to SOAP 1.2? So I could use the soapAction attribute alone in a WSDL for a SOAP 1.1 binding and it would work?
        Hide
        Magesh Bojan
        added a comment -

        Sorry for the confusion. I missed to read the bold not and assumed it worked by default for SOAP 1.1, wish it did

        Changing it to bug.

        Show
        Magesh Bojan
        added a comment - Sorry for the confusion. I missed to read the bold not and assumed it worked by default for SOAP 1.1, wish it did Changing it to bug.
        Hide
        Keith Babo
        added a comment -

        pushed

        Show
        Keith Babo
        added a comment - pushed

          People

          • Assignee:
            Magesh Bojan
            Reporter:
            Keith Babo
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: