Re: Calling a method on a webservice
- From: "John Saunders" <john.saunders at trizetto.com>
- Date: Fri, 30 Mar 2007 15:43:05 -0400
"Scott Holman" <sholman@xxxxxxxxxx> wrote in message
news:OvLaPxscHHA.4864@xxxxxxxxxxxxxxxxxxxxxxx
As john pointed out the classes are not the same. If your using WCF it is
fairly easy to modify the generated proxy code and replace class
implementations. If you are using pre .net3.0 web services you may be
able to do something similar.
You need to modify the generated client proxy class and replace the
generated LogService.Window class with House.Window. You need to make
sure that your implementation of House.Window is decorated with the same
attributes as the class in the generated client proxy. After applying the
same attributes you then need to modify the generated client proxy class
to use House.Window instead of LogService.Window.
To my mind, it would be safer not to edit the proxy class, as it is a
generated class. Instead, yes, create a copy constructor.
John
.
- References:
- Calling a method on a webservice
- From: bjornms
- Re: Calling a method on a webservice
- From: John Saunders
- Re: Calling a method on a webservice
- From: bjornms
- Re: Calling a method on a webservice
- From: Scott Holman
- Calling a method on a webservice
- Prev by Date: RE: Can't see public method on object returned from web service
- Previous by thread: Re: Calling a method on a webservice
- Next by thread: SoapHttpClientProtocol thread safety issue
- Index(es):
Relevant Pages
|