[Mono-bugs] [Bug 65929][Maj] New - SoapHttpClientProtocol::Invoke returns XmlNode instead of system type

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 14 Sep 2004 08:43:13 -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 yjost@perinfo.com.

http://bugzilla.ximian.com/show_bug.cgi?id=65929

--- shadow/65929	2004-09-14 08:43:13.000000000 -0400
+++ shadow/65929.tmp.24304	2004-09-14 08:43:13.000000000 -0400
@@ -0,0 +1,47 @@
+Bug#: 65929
+Product: Mono: Class Libraries
+Version: unspecified
+OS: Mandrake 8.1
+OS Details: kernel version 2.4.18
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Major
+Component: Sys.Web
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: yjost@perinfo.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary:  SoapHttpClientProtocol::Invoke returns XmlNode instead of system type
+
+Description of Problem:
+I noticed a strange behaviour of my mono proxy when trying to use a gSOAP-
+generated WebService with Mono.
+It is similar to bug #49729
+( http://bugzilla.ximian.com/show_bug.cgi?id=49729 ). But I think this one
+has been fixed in the release I'm using (Mono 1.0.1)
+
+Steps to reproduce the problem:
+1. Use the attached WSDL file to generate a C# proxy with wsdl
+2. Place the attached calc.static.cgi file in the cgi-bin directory of a 
+running apache
+3. Modify the proxy accordingly to your server settings
+2. Use the generated class in a program and call one of the methods of the 
+Calculator Proxy Object
+
+Actual Results:
+You will get System.InvalidCastException when trying to cast the result of 
+SoapHttpClientProtocol::Invoke to a double. In fact it return a System.Xml.
+XmlNode[]
+
+Expected Results:
+SoapHttpClientProtocol::Invoke should return a array containing a double in 
+the first cell. 
+
+How often does this happen? 
+Everytime on Mono, never with .NET Framework 1.0.3705
+
+Additional Information:
+This may be a deserialization problem like bug #49729