[Mono-bugs] [Bug 51850][Nor] New - Another Bug when hitting WebLogic Web Service

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 8 Dec 2003 00:23:43 -0500 (EST)

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 davidandrewtaylor@hotmail.com.


--- shadow/51850	2003-12-08 00:23:43.000000000 -0500
+++ shadow/51850.tmp.25874	2003-12-08 00:23:43.000000000 -0500
@@ -0,0 +1,57 @@
+Bug#: 51850
+Product: Mono/Class Libraries
+Version: unspecified
+OS Details: 
+Status: NEW   
+Priority: Normal
+Component: System.Web
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: davidandrewtaylor@hotmail.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+Summary: Another Bug when hitting WebLogic Web Service
+Description of Problem:
+I have submitted other reports documenting problems using MONO as a 
+client against servers other than MS.NET.  Here is a futher example of a 
+public web service (running on WebLogic) but the bug is different (it 
+returns instead of frezing indefinately).  In this case it returns with a 
+NULL result instead of the string expected "10040000", which is returned 
+correctly when run on the MS.NET implementation.
+Steps to reproduce the problem:
+1. Generate a proxy from this URL using the WSDL tool:
+wsdl http://appserver.pepperzak.net/bankcode/BankCodeEJBHome/wsdl.jsp
+2. Run this code against it:
+using System;
+public class test
+  public static void Main()
+  {
+    Console.WriteLine("Starting");
+    BankCode service = new BankCode();
+    Console.WriteLine(service.getCodeByName("Commerzbank"));
+  }
+Actual Results:
+Nothing printed (because a null value is returned from the method).
+Expected Results:
+this string --> "10040000" (which is correctly returned if you try this 
+on the MS.NET client).
+Additional Information:
+I am having no luck at all using MONO as a client to hit Web Services 
+hosted by AXIS or BEA WebLogic.  I would take a wild stab-in-the-dark 
+that a lot of the current MONO web service client code is currently 
+assuming the SOAP format will be exactly the same as outputted by MS.NET 
+when run on the server side.  We need to make sure MONO is tested against 
+a reasonable range of web service servers.