[Mono-bugs] [Bug 58543][Nor] New - MONO Beta 1 Bug in WSDL tool when trying to generate proxy against BEA WebLogic
Sat, 15 May 2004 03:54:53 -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 email@example.com.
--- shadow/58543 2004-05-15 03:54:53.000000000 -0400
+++ shadow/58543.tmp.16309 2004-05-15 03:54:53.000000000 -0400
@@ -0,0 +1,63 @@
+Product: Mono: Class Libraries
+OS: Red Hat 9.0
+Severity: 002 Two hours
+Summary: MONO Beta 1 Bug in WSDL tool when trying to generate proxy against BEA WebLogic
+Description of Problem:
+Exception is thrown when trying to generate web service proxy from MONO
+using the WSDL tool. Problem only occurs when directly accessing BEA
+WebLogic AND with HTTP BASIC Auth, and it does not matter if the web
+services are using Apache Axis or BEA's own Web Service infrastructure.
+What makes this problem more complex is that 1/10 attempts the proxy is
+generated with no errors, and about 9 times out of 10 product this error,
+so if you keep trying long enough eventually the class is correctly
+* This problem NEVER occurs using MS.NET implementation of WSDL.
+* Problem does NOT occur if Apache is used to proxy the requests into BEA
+* Problem seems to be independent of the Web Service stack (doesnt make
+any different if using Apache Axis or BEA's Web Logic Stack), so it is
+unlikely the Java Web Services stack is causing problems.
+* Problem only occurs when HTTP BASIC AUTH is used.
+Steps to reproduce the problem:
+Used WSDL command line tool, however this BEA instance is behind our
+companies firewall, so I have attached a TCP dump so you can actually see
+Mono Web Services Description Language Utility
+Error: System.Xml.XmlException: Document element did not appear.
+in <0x00250> System.Xml.XmlTextReader:Read ()
+in <0x00087> System.Xml.XmlReader:MoveToContent ()
+in <0x00058> (wrapper remoting-invoke-with-check)
+in <0x000f5> Mono.WebServices.Driver:Run (string)
+It should generate a .cs proxy.
+How often does this happen?
+about 9 times out of 10. If I keep trying it actually works
+approximately 1 time out of 10. However this bug has always been in MONO
+(it was not recently introduced) and I have observed this intermittent
+behavious over many months.
+Please see the attached TCP Dump