WseWsdl3 Issue Creating C# proxy multiple parameters

[geobier]

This is a similar to a question asked by somone else on 7/3.

We have a fairly complicated WSE enabled set of Web Services. When
wsdl.exe is used to generate the client proxy and server interface, no errors
are reported, the code works fine.

Using WseWsdl3.exe to try and generate a secure client proxy results in the
following error:

Error: Unable to import binding 'InterfaceServiceSoap' from namespace
'http://somecompany.com/omx'.
- Unable to import Operation: 'getCatalogDataRange'
- Found more than one parameter on method getCatalogDataRange while
multiple parameters are not supported.

If the client code uses the Visual Studio 2005 IDE to add the web reference,
no problem is reported and the service works when using the Wse derived proxy
class.

I tried feeding into wsewsdl3.exe the output from the web service directly:

wsewsdl3.exe http://localhost/SomeService/SomeService.asmx?wsdl

and got the same error message about multiple parameters not supported.

My conclusion is that whatever is generating the client proxy when inside
the Visual Studio 2005 IDE is not behaving identically to the WseWsdl3
program.

Any help in identifying the issue when running WwseWsdl3.exe externally
would be appreciated.

thanks,
--george

[geobier]

This problem is solved.

I needed to add the command line argument /type:webClient to have the
behavior more or less agree with the Visual Studio IDE.

There is still a little bit of mystery in regards to the generation of the
classes.

If the service is named MyService then the Visual Studio add WebReference
generates a

MyService.MyServiceWSE

class to get to the secure methods. The standalone wsewsdl3.exe program
does not. So there is still a little bit of difference in behavior. Anyone
know what Visual Studio is really doing compared to wsewsdl3.exe?

thanks,
--george

--
thanks,
--george

[Moin Ahmed]

Well the answer is really simple, to make distinction b/w client proxy inherited by SoapHttpClientProtocol & WebServicesClientProtocol, visual studio generates later one with different name; thats why at any time u can make use of both...
while on the other end, wsewsdl3 tool doesnt care about any naming & generates the servicename as it reads from wsdl...

Feel free to email me if you have any other query.:)

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.

[mikesloper]

I'm not a windows person but I had to write a WSDL for some VB client. I found out after reading: http://msdn.microsoft.com/en-us/library/aa529578.aspx that if /type:webClient is not set, methods/opertations can only take one parameter.

From http://www.developmentnow.com/g/28_2006_7_0_0_785679/WseWsdl3-Issue-Creating-C-proxy-multiple-parameters.htm

Posted via DevelopmentNow.com Groups
http://www.developmentnow.com/g/