Hi Chris, Thanks for your reply. XML conforms to a schema. If I add schema elements it works. Since my service is Axis Message Style (Passing in and out w3c.org.dom.document), I had the impression type should be any type or what type should I use if my parameter and return type are w3c.org.dom.document?
Thanks, Ranjith Pillai. -----Original Message----- From: Chris Haddad [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 7:05 PM To: [EMAIL PROTECTED] Subject: Re: .NET Client -> Axis Web service -Issue with "anyType" if the XML document conforms to a XML Schema definition, just replace the anyType reference in the WSDL with the schema element reference. /Chris ---------- Original Message ---------------------------------- From: "Pillai, Ranjith" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Fri, 2 Apr 2004 10:53:48 -0800 >Hi Axis Community, > > This is not generally an Axis question, .NET Client >question. But there are many experts here who already done .NET Client >-> Axis Web service invocation, hope someone can help me. > > The problem is my Axis web service returns an XML Document >object (Axis message style) and its type is "anyType" in WSDL. When >.NET Client invokes my service what it gets back is an "Object" since >type is "anyType". When debugging this Object shows "undefined value". >TCPMon shows the output message correctly. What is going wrong here? >Or how do I tell .NET Client that what my service is sending back is an >XML Document rather than any specific bean type? > > > >Any help will be deeply appreciated. > >Thanks, > >Ranjith Pillai. > > >
