The custom types in WSDL generated classes (proxy classes) contain public
type declarations for properties. If you need properties (as in get and set)
instead, you can do one of the two:
1. Have a translator that takes the values from the proxy generated type and
sets them in another custom object at the client.
2. This is a hack -- you will need to modify the proxy class manually!
Instead of using the proxy generated types, you could reference the custom
type at the client (using the "using" statement). Then delete/comment the
proxy generated type definition in the proxy class file. The downside to
this is you will have to distribute the type library to the client, which
defeats the purpose of a web service being loosely coupled. You could also
try distributing interfaces instead (although I have not tried this)
--
Manohar Kamath
Editor, .netWire
www.dotnetwire.com
"Sumit" <Su***@discussions.microsoft.com> wrote in message
news:52**********************************@microsof t.com...
Hi All...
What is the best way of binding a custom object that is returned via a Web
Service?
From what Ive seen, the proxy class generated by wsdl.exe doesnt include
properties for the members of the custom object, it only contains the
variable declarations. Does the wsdl.exe that comes with WSE handle this
differently? Is there some other mechanism I can use besides writing a
custom decorator for wsdl.exe to generate proxy classes that have properties?
