[ https://jira.jboss.org/browse/JBTM-778?page=com.atlassian.jira.plugin.sys... ] Andrew Dinn commented on JBTM-778: ---------------------------------- No, this is not the parsing problem I mentioned. However, I think that you are right that the name needs to be a simple string. Also, the name needs to be declared in the port type declared in the imported file wsat.wsdl. Now this file is a copy of the OASIS wsdl which does not provide names for inputs/outputs in the port declarations just message types. So, mentioning a name in the bindings is not an option without modifying the OASIS wsdl. I would rather not do that since this is what is defined by the spec. I don't think this presents a problem because you can also specify the binding inputs and outputs without using a name attribute e.g. <wsdl:operation name="AbortedOperation"> <soap:operation soapAction="http://docs.oasis-open.org/ws-tx/wsat/2006/06/Aborted" style="document"/> <wsdl:input> <soap:body use="literal"/> </wsdl:input> </wsdl:operation> The input message type should still be determined correctly using the information provided in the port type and the name should still default to the unqualified name of the message type. So, I think the required fix is just to remove the message=.. .attributes from the binding:operation:input/output elements. -- 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

[ https://jira.jboss.org/browse/JBTM-778?page=com.atlassian.jira.plugin.sys... ] Mauro Molinari edited comment on JBTM-778 at 8/20/10 5:49 AM: -------------------------------------------------------------- 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... was (Author: mauromol): 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... -- 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

[ https://jira.jboss.org/browse/JBTM-778?page=com.atlassian.jira.plugin.sys... ] Mauro Molinari commented on JBTM-778: ------------------------------------- I found the problem, that's my fault: I looked at the wrong type definition. The correct one to look at is that defining the type for the input element of the tBindingOperation type, which is tBindingOperationMessage: <xs:complexType name="tBindingOperationMessage"> <xs:complexContent> <xs:extension base="wsdl:tExtensibleDocumented"> <xs:attribute name="name" type="xs:NCName" use="optional"/> </xs:extension> </xs:complexContent> </xs:complexType> So, here the name attribute is optional and the WSDL parser is coherent. Anyway, please note that trying your original fix (<wsdl:input name="wsat:Committed"> ), when exposing the web service CXF does not agree: [cut] Caused by: java.lang.IllegalArgumentException: An operation with name [{http://docs.oasis-open.org/ws-tx/wsat/2006/06}CommittedOperation] already exists in this service at org.apache.cxf.service.model.InterfaceInfo.addOperation(InterfaceInfo.java:71) [cut] So the actual fix must be that of just removing the message attribute, as you said. -- 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