Jan 31, 2009 07:49 PM|johnwsaunders3|LINK
The namespace should have been fixed before the code went into production. Now you're stuck with it until you can change all of the clients. They, of course, still use the old namespace.
What you need to look at is not the generated code, but the WSDL. Open the .ASMX file in the browser and click the link to view the entire service description. You can save it to a file to examine in your favorite editor, if you like. You'll be looking near
the bottom, inside of wsdl:binding, for a wsdl:operation that matches the method you're having trouble with. There should be a soap:operation element inside of it with a soapAction attribute. This is what the client
should be sending to the server. For example:
<wsdl:binding name="ArrayServiceSoap" type="tns:ArrayServiceSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
<soap:operation soapAction="http://tempuri.org/AddUsersToRoles" style="document" />
You can look at the traffic on the wire to see what the client is actually sending. See
Ways to See SOAP Traffic for some ideas on how to do that.