[Mono-bugs] [Bug 57785][Maj] Changed - Web service call fails with XmlElement return type
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Thu, 6 May 2004 11:33:38 -0400 (EDT)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by photon@seznam.cz.
http://bugzilla.ximian.com/show_bug.cgi?id=57785
--- shadow/57785 2004-05-05 10:31:14.000000000 -0400
+++ shadow/57785.tmp.12910 2004-05-06 11:33:38.000000000 -0400
@@ -141,6 +141,79 @@
Does the test case work if you use the web service proxy generated by
MS.NET instead of the one generated by mono?
------- Additional Comments From lluis@ximian.com 2004-05-05 10:31 -------
Ok, I commited a fix for wsdl.exe and for the web service client. Can
you confirm it is working with current CVS? Thanks.
+
+------- Additional Comments From photon@seznam.cz 2004-05-06 11:33 -------
+I have used the newest CVS. Now the web service call is made and
+result returned but a new exception is thrown when mono parses the result.
+
+System.NotSupportedException: Data type 'Result' not supported: in
+<0x00080> System.Xml.Serialization.TypeTranslator:GetPrimitiveTypeData
+(string)
+in <0x00098>
+System.Xml.Serialization.XmlSerializationReader:ReadTypedPrimitive
+(System.Xml.XmlQualifiedName)
+in <0x00256>
+System.Xml.Serialization.XmlSerializationReader:ReadReferencingElement
+(string,string,bool,string&)
+in <0x00070>
+System.Xml.Serialization.XmlSerializationReader:ReadReferencingElement
+(string&)
+in <0x02189>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadMembers
+(System.Xml.Serialization.ClassMap,object,bool,bool)
+in <0x0026c>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadMessage
+(System.Xml.Serialization.XmlMembersMapping)
+in <0x000f2>
+System.Xml.Serialization.XmlSerializationReaderInterpreter:ReadRoot ()
+in <0x00086> System.Xml.Serialization.XmlSerializer:Deserialize
+(System.Xml.Serialization.XmlSerializationReader)
+in <0x00056> System.Xml.Serialization.XmlSerializer:Deserialize
+(System.Xml.XmlReader)
+in <0x000fd>
+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 <0x00335>
+System.Web.Services.Protocols.SoapHttpClientProtocol:ReceiveResponse
+(System.Net.WebResponse,System.Web.Services.Protocols.SoapClientMessage,System.Web.Services.Protocols.SoapExtension[])
+in <0x0007d> (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 <0x002ce>
+System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke
+(string,object[])
+in <0x0006b> (wrapper remoting-invoke-with-check)
+System.Web.Services.Protocols.SoapHttpClientProtocol:Invoke
+(string,object[])
+in <0x0006b> Testing:GetCrc (string,string)
+
+Executing binary compiled with VS.NET generates the same exception,
+the same binary works without problems on Windows.
+
+
+Captured WS call response:
+
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<SOAP-ENV:Envelope
+SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
+xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
+<SOAP-ENV:Body><SOAPSDK1:GetCrcResponse
+xmlns:SOAPSDK1="http://tempuri.org/message/">
+<Result>
+ <chss_result>
+ <version>2.1.0</version>
+ <status>
+ <code>0</code>
+ <message>OK</message>
+ </status>
+ <CRC>3261</CRC>
+ </chss_result>
+</Result>
+</SOAPSDK1:GetCrcResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
+
+
+Sorry, but I cannot provide a working test case for this.
+