|I'm trying to develop an XML Webservice for work that uses SOAP. It's very easy to get something going quickly, but It's a bit tougher to get it exactly like you want .
My current concern is the WSDL that's automatically generated with the "?WSDL" query string is very unstrict (can't blame it, it's not psychic). For instance, every parameter to a method that can be null ends up having its "minOccurs" set to 0. I'd also really like to be able to use some regular expression restrictions for certain types. I'm a big believer in schema validation (which I realize I have to do by hand regardless of what the WSDL says), and I'd like the WSDL to be more strict.
I've searched for quite a while, and I'm not having much luck finding anything. There seems to be a lot of attributes I can use to control the XML serialization of classes, but I haven't seen anything yet that lets me do something like "represent this class with this XmlSchema instance", which might be how I would get my service to create a "good" schema (guessing here).
Should I just give up on making the automatically generated WSDL look good and just write my own WSDL file by hand (and point clients there). It seems like that route would be more of a pain in the butt to maintain, but if that's the only way to make me happy I might go that route. Is there any way I can turn off the automatic WSDL generation (?WSDL querystring on the .asmx) if I go that route?
I, for one, do not think the problem was that the band was down. I think that the problem may have been that there was a Stonehenge monument on the stage that was in danger of being crushed by a dwarf.
-David St. Hubbins