[Mono-bugs] [Bug 51850][Nor] New - Another Bug when hitting WebLogic Web Service
Thu, 5 Feb 2004 00:37:24 -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 firstname.lastname@example.org.
--- shadow/51850 2004-02-05 00:37:24.000000000 -0500
+++ shadow/51850.tmp.21412 2004-02-05 00:37:24.000000000 -0500
@@ -0,0 +1,77 @@
+Product: Mono/Class Libraries
+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:
+2. Run this code against it:
+public class test
+ public static void Main()
+ BankCode service = new BankCode();
+Nothing printed (because a null value is returned from the method).
+this string --> "10040000" (which is correctly returned if you try this
+on the MS.NET client).
+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.
+------- Additional Comments From email@example.com 2003-12-08 09:51 -------
+This is now fixed in cvs.
+> 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
+That's not true. The client code is not assuming any specific SOAP
+format. But since it has been tested mainly on .NET servers, it is
+normal find new bugs when testing against other servers.
+> We need to make sure MONO is tested against a reasonable
+> range of web service servers.
+I Agree, and your help here is very valuable.