But if the general rule is not to use xsd:any or xsd:anyType, what is the preferred mode of exchanging an arbitrary xml document using doc/lit mode?
If I do not want to use axis message style, how should I construct my WSDL so that I can accept and return an arbitrary xml document? Shantanu > ________________________________ > > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Monday, November 14, 2005 4:27 AM > To: [email protected] > Subject: Re: How to handle xsd:anyType with Message Style web services ? > > > As I said, the .NET client can construct the XML document and stuff it > into a SOAP envelope using DOM with the System.XML API. But is it really > necessary? How is the .NET client supposed to know what to send you? > > Is the document truly of xsd:anyType? Do you really not know in advance > what the type of "in0" should be? If there is a predefined structure, > then your WSDL should define that structure -- regardless of how you've > elected to process it on the server side (message style vs document or > wrapped). > > If you choose to use the message style, then you should edit the > generated WSDL and add the appropriate schema definitions so that > clients can more easily communicate with you. > > As a general rule, you shouldn't use <xsd:any>, <xsd:anyType>, or > <xsd:anyAttribute> in your WSDL. > > Anne > > > On 11/13/05, Kr <[EMAIL PROTECTED]> wrote: > > Thank you Anne. > > For my AXIS message style web service, the AXIS generated WSDL > has > <element name="in0" type="xsd:anyType"/> and can .NET consumer > support > this xsd:anyType and pass in an xml document using the generated > stubs > out of such WSDL's ? > > > >
