Hey Simon,
another way is to just morph the WSDL so that rather than retrieving a
strongly typed complexType, you are receiving just XmlElement.
This is sort of related:
http://msdn.microsoft.com/library/en...ce04162003.asp
But in your case, you are building clients. So what you want to do is
change the existing WSDL so that the response element is an xsd:any.
Replace this:
<s:element name="MethodResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="whatever"
type="ns1:CustomComplexType" />
</s:sequence>
</s:complexType>
</s:element>
....with something like this:
<s:element name="MethodResponse">
<s:complexType>
<s:sequence>
<s:any minOccurs="0" maxOccurs="1" />
</s:sequence>
</s:complexType>
</s:element>
Then, generate the client-side proxies from this generic-ized WSDL. Your
client-side proxy will get a System.Xml.XmlElement for each webmethod
invocation. This element contains the raw XML response.
-Dino
dinoch // microsoft.com
"erymuzuan" <er*******@yahoo.com> wrote in message
news:42**************@yahoo.com...
SoapExtension, will give you the flexibilty to get to the raw soap
messages,
http://msdn.microsoft.com/library/de...classtopic.asp
regards
erymuzuan mustapa
Simon wrote: Hello,
I have some web services which return quite large XML documents. I want
to invoke the services and retrieve the raw XML in order to persist it
through an XML database. I don't want to create a bunch of meaningless
proxy classes.
It seems like this should be quite simple; I would appreciate some
pointers!
Thanks,
Simon
