WSDL proxy issue!

  • Thread starter Thread starter Raj
  • Start date Start date
R

Raj

Here's the signature of the web service i have created:

using WebServiceData;

[SoapHeader("Consumer")]
[WebMethod]
public WebServiceData.Result PutData(WebServiceData.Result res)
{

}

The proxy file generated by wsdl always generates the above function as
public Result PutData(Result)

And hence, after the proxy file is generated every time i need manually
replace Result with WebServiceData.Result otherwise I am getting error while
consuming the web service

Here's the command I have used to generate the proxy file:

wsdl http://../../filename.asmx?WSDL

It is creating successfuly without any error!

I welcome any workaround

Thank you

Regards
Raj
 
Here's the signature of the web service i have created:

using WebServiceData;

[SoapHeader("Consumer")]
[WebMethod]
public WebServiceData.Result PutData(WebServiceData.Result res)
{

}

The proxy file generated by wsdl always generates the above function as
public Result PutData(Result)

And hence, after the proxy file is generated every time i need manually
replace Result with WebServiceData.Result otherwise I am getting error while
consuming the web service

Here's the command I have used to generate the proxy file:

wsdl http://../../filename.asmx?WSDL

It is creating successfuly without any error!

I welcome any workaround

Thank you

Regards
Raj
Click to expand...

My experience when adding the web reference is that I need to supply a
namespace. It would have defaulted to the site name, I believe, unless
the web service is in the same solution, then I'm unsure how the
namespace defaults.

In general though, I feel the client should assign a meaningful name to
the web service namespace, not the service forcing the namespace.
 
Back
Top