Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-778

WSDL bindings in XTS code employ the wrong attribute in the binding:operation:input/output declarations

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.13.0
    • 4.12.0
    • XTS
    • None

      The WSDL for the WSTX service bindings employs the invalid attribute "message" for the binding:operation:input and binding:operation:output elements. The correct attribute name is "name". e.g. in wscoor-activation-binding.wsdl the declaration is

      <wsdl:binding name="Activation_SOAPBinding" type="wscoor:ActivationPortType">
      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="CreateCoordinationContextOperation">
      <wsdl:input message="wscoor:CreateCoordinationContext">
      <soap:body use="literal"/>
      </wsdl:input>
      <wsdl:output message="wscoor:CreateCoordinationContextResponse">
      <soap:body use="literal"/>
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>

      The correct version should be

      <wsdl:binding name="Activation_SOAPBinding" type="wscoor:ActivationPortType">
      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
      <wsdl:operation name="CreateCoordinationContextOperation">
      <wsdl:input name="wscoor:CreateCoordinationContext">
      <soap:body use="literal"/>
      </wsdl:input>
      <wsdl:output name="wscoor:CreateCoordinationContextResponse">
      <soap:body use="literal"/>
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>

      According to a comment in the flle this was a workaround for an error in the com.ibm.wsdl parsing which now appears to have been fixed. The WSDL should be updated accordingly.

              rhn-engineering-adinn Andrew Dinn
              rhn-engineering-adinn Andrew Dinn
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: