cjard
April 30th, 2009, 10:02 AM
Guys
I have a spec that lays out the XML schema that a webservice must accept and return, and now I need to create that webservice (to replace a service that we do not have the source code for)
Would anyone care to give any pointers as to how to go about creating a web service in C# and then getting control ove rthe XML serialization such that I can ensure the input and output XML matches the spec exactly?
I'm familiar with the process from the opposite side of the coin, in that I've made a set of classes with [XmlXXX] attributes on the properties and methods etc to control ser/deser and then posted the serialized XML for these these off via a WebRequest and deserialize dthe response, but foraying into writing a webservice to sit within IIS is a new perspective for me
All the reading material I have consumed so far has been concerned with making the code, and forget what the xml looks like because the client stub generator linking to the WSDL will take care of it.. I kinda have to integrate with an existing platform in the client, and shape the server around what is already implemented so having fine grained control over the XML is a must
Cheers for any tips
cj
I have a spec that lays out the XML schema that a webservice must accept and return, and now I need to create that webservice (to replace a service that we do not have the source code for)
Would anyone care to give any pointers as to how to go about creating a web service in C# and then getting control ove rthe XML serialization such that I can ensure the input and output XML matches the spec exactly?
I'm familiar with the process from the opposite side of the coin, in that I've made a set of classes with [XmlXXX] attributes on the properties and methods etc to control ser/deser and then posted the serialized XML for these these off via a WebRequest and deserialize dthe response, but foraying into writing a webservice to sit within IIS is a new perspective for me
All the reading material I have consumed so far has been concerned with making the code, and forget what the xml looks like because the client stub generator linking to the WSDL will take care of it.. I kinda have to integrate with an existing platform in the client, and shape the server around what is already implemented so having fine grained control over the XML is a must
Cheers for any tips
cj