Issues with. NET calling Java-generated WS-R2718

From Http://blog.csdn.net/cyq1984/article/details/17120097java project, use EASYWSDL to generate the WSDL for the published webservice. The data is described using the Service data object model of SDO. The generated WSDL uses the VS2010 Visual Studio command prompt line to generate a C # related call file using the WSDL out command and discovers that the background throws the following message: Warning: This WEB reference does not conform to the WS-I Basic profile v1.1. R2718: The wsdl:binding in the description must contain the same set of Wsdl:operations as the referenced wsdl:porttype. -The operation "Operation1" on the PortType "Componentservice1interface" from the namespace "Http://www.com/esb/ComponentService1" does not have a matching binding. -On PortType "Componentservice1interface" from the Namespace "Http://www.com/esb/ComponentService1", there is no relation from the namespace "http://www.com/ Esb/componentservice1 "Operation1" matches the operation "Componentservice1soap11" on the "binding". -On PortType "Componentservice1interface" from the Namespace "Http://www.com/esb/ComponentService1", there is no relation from the namespace "http://www.com/ Esb/componentservice1 "Operation1" matches the operation "Componentservice1soap11" on the "binding". For more details about the WS-I Basic profile v1.1, see the specification at the following location: Http://www.ws-i.org/Profiles/BasicProfile-1.1.html. Error: Unable to import binding "Componentservice1soap11" from Namespace "Http://www.com/esb/ComponentService1". -From the namespace "Http://www.com/esb/ComponentSThe following syntax error exists in the operation "Operation1" on Ervice1 "Componentservice1interface" PortType: There is no matching binding for this operation. Check that the operation, input, and output names in the Binding section match the corresponding names in the PortType section. It seems that the generated WSDL does not conform to some of WS's Specifications (. NET validation of these things is really strict), but it has never encountered such a problem in Java. Research related norms and network resource learning, the root cause of the problem is the description of the following "PortType" fragment in the WSDL file: [HTML] View plain copy Description of the following "binding" section: [HTML] View plain copy The "input" and "output" contents of the two are inconsistent with the name attribute (so-called inconsistency, that is, the former has the name attribute value, the latter does not). After trying, we found that there are two solutions: 1. The name attribute value of input and output of the former is removed. 2. Add the same name attribute value as the former in input and output of the latter. The adjusted fragment is: [HTML] View plain copy or [HTML] view plain copy In short, it is necessary that both input and output properties remain fully consistent.

(GO). NET calls to Java-generated WS-R2718 issues