Flatten WSDL

[johns1111]

The WSDL reflects the full inheritance structure of my program, how can
I flatten the WSDL file?

e.g. if I have a class A with properties PA1 and PA2 and a class B
which in the C# code inherits from A and properties PB1 and PB2, then
the WSDL for a web service containing a method that returns be contains
complexType B with extension base A.
I want to suppress that to hide the inheritance structure of the
classes, also the client of the web service has absolutely no use for
this information as a complextType B containing the properties PA1,
PA2, PB1 and PB2 would be serialized exactly the same way.

[John Saunders]

<jo*******@gmx.dewrote in message
news:11**********************@i3g2000cwc.googlegro ups.com...

The WSDL reflects the full inheritance structure of my program, how can
I flatten the WSDL file?

e.g. if I have a class A with properties PA1 and PA2 and a class B
which in the C# code inherits from A and properties PB1 and PB2, then
the WSDL for a web service containing a method that returns be contains
complexType B with extension base A.
I want to suppress that to hide the inheritance structure of the
classes, also the client of the web service has absolutely no use for
this information as a complextType B containing the properties PA1,
PA2, PB1 and PB2 would be serialized exactly the same way.

If you write the WSDL and its schemas by hand, you can get exactly what you
want.

John

[Mathieu Cartoixa]

jo*******@gmx.de a écrit :

e.g. if I have a class A with properties PA1 and PA2 and a class B
which in the C# code inherits from A and properties PB1 and PB2, then
the WSDL for a web service containing a method that returns be contains
complexType B with extension base A.
I want to suppress that to hide the inheritance structure of the
classes, also the client of the web service has absolutely no use for
this information as a complextType B containing the properties PA1,
PA2, PB1 and PB2 would be serialized exactly the same way.

Maybe you can customize the serialization process (see IXmlSerializable).

Mathieu

[johns1111]

>
If you write the WSDL and its schemas by hand, you can get exactly what you
want.

John

Thanks for the reply. That brings me to the question: If I have my own
schema how do I include it/use it with my web service. Currently the
web.config just specifies which DLLs to include and the asmx files just
contain one line, e.g.
<%@ WebService Language="C#" CodeBehind="" Class="Runtime" %>

Where would I specify that I want to use my own WSDL file for a web
service?

[John Saunders]

<jo*******@gmx.dewrote in message
news:11**********************@k70g2000cwa.googlegr oups.com...

>

>>
If you write the WSDL and its schemas by hand, you can get exactly what
you
want.

John

Thanks for the reply. That brings me to the question: If I have my own
schema how do I include it/use it with my web service. Currently the
web.config just specifies which DLLs to include and the asmx files just
contain one line, e.g.
<%@ WebService Language="C#" CodeBehind="" Class="Runtime" %>

Where would I specify that I want to use my own WSDL file for a web
service?

You'll have to define what you mean by "use my own WSDL".

If you have your own WSDL and you send it to your customers, then that's
what they'll have to use. You then make sure that your web service conforms
the the WSDL, and it will be up to them to make sure that their client
conforms to the WSDL, and then everything will "just work".

;-)
You may mean to ask, "how do I get http://host/Runtime.asmx?WSDL" to return
my own WSDL, and the answer is that I don't know. I turn that feature off:

<configuration>
<system.web>
<webServices>
<protocols>
<remove name="Documentation" />
<remove name="HttpGet" />
<remove name="HttpPost" />
</protocols>
</webServices>
<system.web>
</configuration>

Good Luck,
John