Any way to control generated webservice WSDL?

[Peter McEvoy]

Hi all,
another question related to Schema and WSDL...

I'd like to have a bit more control over the WSDL that is generated for my
..asmx. In particular, I'd like to override the generated WSDL with a
handmade one that I want to provide.

The reasons for this are:
1) My handmade WSDL (which will be based on the machine generated WSDL) will
include alot more annotation elements - descriptions of the fields and types
and enums etc. basically richer information that can be viewd by developers
wishing to use my web methods.

2) I'd like to have the handmade WSDL use import elements to import my
handcrafted schema files: I am finding that the machine generated message
definitions are not strong enough in terms of constraints etc, and since my
server side objects are generated directly from the schema using XsdObjGen, I
see no reason why client proxies can't be generated directly from the
original schema as well - I want to allow the consumers of my webservice to
generate their own client proxies using the best tools availble for their
platform/language: I would rather they accessed the original schema than the
second hand automatic schema definition generated by my webservice.

3) The handmade WSDL will be a static file, and thus serving it up won't
consume server resources (I know, this is a minor thing...)

Anyway, if anyone has any ideas how I can go about this...

Pete

[Dino Chiesa [Microsoft]]

Hmm, yes.
turn off dynamic WSDL generation.
Post your static WSDL file to the site

see also:
http://tinyurl.com/4gm4o

-Dino
"Peter McEvoy" <Pe*********@discussions.microsoft.com> wrote in message
news:1A**********************************@microsof t.com...

Hi all,
another question related to Schema and WSDL...

I'd like to have a bit more control over the WSDL that is generated for my
.asmx. In particular, I'd like to override the generated WSDL with a
handmade one that I want to provide.

The reasons for this are:
1) My handmade WSDL (which will be based on the machine generated WSDL)
will
include alot more annotation elements - descriptions of the fields and
types
and enums etc. basically richer information that can be viewd by
developers
wishing to use my web methods.

2) I'd like to have the handmade WSDL use import elements to import my
handcrafted schema files: I am finding that the machine generated message
definitions are not strong enough in terms of constraints etc, and since
my
server side objects are generated directly from the schema using
XsdObjGen, I
see no reason why client proxies can't be generated directly from the
original schema as well - I want to allow the consumers of my webservice
to
generate their own client proxies using the best tools availble for their
platform/language: I would rather they accessed the original schema than
the
second hand automatic schema definition generated by my webservice.

3) The handmade WSDL will be a static file, and thus serving it up won't
consume server resources (I know, this is a minor thing...)

Anyway, if anyone has any ideas how I can go about this...

Pete