The text of this article is not in this database — only its details are. Read it on the old site: Method Overloading in WebServices
1 Comment
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
The text of this article is not in this database — only its details are. Read it on the old site: Method Overloading in WebServices
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
Timothy PowerPosted May 14, 2013, 8:44 AM
I tried this and it puked during wsdl creation referencing it from another project. I got the following error message. Service 'PHIForestryWS.ProcessAXF' does not conform to WS-I Basic Profile v1.1. Please examine each of the normative statement violations below. To turn off conformance check set the ConformanceClaims property on corresponding WebServiceBinding attribute to WsiClaims.None. R2304: Operation name overloading in a wsdl:portType is disallowed by the Profile. A wsdl:portType in a DESCRIPTION MUST have operations with distinct values for their name attributes. Note that this requirement applies only to the wsdl:operations within a given wsdl:portType. A wsdl:portType may have wsdl:operations with names that are the same as those found in other wsdl:portTypes. - Operation 'InsertInspector' on portType 'ProcessAXFSoap' from namespace 'http://tempuri.org/'. - Operation 'UpdateInspector' on portType 'ProcessAXFSoap' from namespace 'http://tempuri.org/'. To make service conformant please make sure that all web methods belonging to the same binding have unique names.