[Mono-devel-list] (no subject)

[Neale.Ferguson at SoftwareAG-USA.com]

I ran wsdl against ConverterService.asmx and then used the following simple client code to invoke it:

using System;
using System.Web.Services;

class sample {

        static void Main ()
        {
                double result;

                ConverterService service = new ConverterService();
                service.Login("neale");
                result = service.Convert("USD","GBP",1.0);
                Console.WriteLine("{0}",result.ToString());
        }
}

Unhandled Exception: System.Xml.XmlException: Text node cannot appear in this state.  Line 1, position 1.
in <0x0000006e> System.Xml.XmlTextReader:ReadText (bool)
in <0x000003b8> System.Xml.XmlTextReader:ReadContent ()
in <0x00000206> System.Xml.XmlTextReader:Read ()
in <0x000000ae> System.Xml.XmlReader:MoveToContent ()
in <0x00000032> System.Web.Services.Protocols.WebServiceHelper:ReadSoapMessage (System.Xml.XmlTextReader,System.Web.Services.Protocols.SoapTypeStubInfo,System.Web.Services.Description.SoapBindingUse,System.Xml.Serialization.XmlSerializer,object&,System.Web.Services.Protocols.SoapHeaderCollection&)
in <0x00000538> System.Web.Services.Protocols.SoapHttpClientProtocol:ReceiveResponse (System.Net.WebResponse,System.Web.Services.Protocols.SoapClientMessage,System.Web.Services.Protocols.SoapExtension[])
in <0x000000f4> (wrapper remoting-invoke-with-check) System.Web.Services.Protocols.SoapHttpClientProtocol:ReceiveResponse (System.Net.WebResponse,System.Web.Services.Protocols.SoapClientMessage,System.Web.Services.Protocols.SoapExtension[])
in <0x000003f2> System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke (string,object[])
in <0x000000d4> (wrapper remoting-invoke-with-check) System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke (string,object[])
in <0x0000007c> ConverterService:Login (string)
in <0x000000ac> (wrapper remoting-invoke-with-check) ConverterService:Login (string)
in <0x0000006a> sample:Main ()

-----Original Message-----
Hi Neale.

This looks similar to a bug I thought it was already fixed in
HttpWebRequest code. Can you reproduce this reliably and share the test
case?