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

[Mauro Molinari (JIRA)]

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

Mauro Molinari commented on JBTM-778:
-------------------------------------

I had a look at http://schemas.xmlsoap.org/wsdl/ and I find the following definition for the operation element in binding:

<xs:complexType name="tBindingOperation">
	<xs:complexContent>
		<xs:extension base="wsdl:tExtensibleDocumented">
			<xs:sequence>
				<xs:element name="input" type="wsdl:tBindingOperationMessage"
					minOccurs="0" />
				<xs:element name="output" type="wsdl:tBindingOperationMessage"
					minOccurs="0" />
				<xs:element name="fault" type="wsdl:tBindingOperationFault"
					minOccurs="0" maxOccurs="unbounded" />
			</xs:sequence>
			<xs:attribute name="name" type="xs:NCName" use="required" />
		</xs:extension>
	</xs:complexContent>
</complexType>

So, it seems like "name" should actually by of type NCName (so, no colons allowed in its value), however what surprises me is that in this schema the "name" attribute is marked as required, although my parser doesn't give any error if I omit it in the WSDL...

> 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