[jbossts-issues] [JBoss JIRA] Commented: (JBTM-778) WSDL bindings in XTS code employ the wrong attribute in the binding:operation:input/output declarations

[Andrew Dinn (JIRA)]

    [ https://jira.jboss.org/browse/JBTM-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12546056#action_12546056 ] 

Andrew Dinn commented on JBTM-778:
----------------------------------

Hmm, that's strange. It may be that enforcement of the required option is ignored precisely to deal  with situations like this where existing WSDL does not provide names in port type declarations. In such cases you just cannot use the original WSDL and still provide a name in the binding. Anyway, it works and it appearsfrom other cases I have looked at that the WS tools and runtime do the right thing. Let's leave the language lawyers to wrangle over this for  now.

> WSDL bindings in XTS code employ the wrong attribute in the binding:operation:input/output declarations
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-778
>                 URL: https://jira.jboss.org/browse/JBTM-778
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: XTS
>    Affects Versions: 4.12.0
>            Reporter: Andrew Dinn
>            Assignee: Andrew Dinn
>             Fix For: 4.13.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira