[Mono-bugs] [Bug 51839][Nor] New - WSDL Tool parse problem with XML Namespaces

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Sun, 7 Dec 2003 20:03:37 -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/51839	2003-12-07 20:03:36.000000000 -0500
+++ shadow/51839.tmp.22950	2003-12-07 20:03:36.000000000 -0500
@@ -0,0 +1,52 @@
+Bug#: 51839
+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: WSDL Tool parse problem with XML Namespaces
+Description of Problem:
+Tried to generate a web service proxy for an apache axis web service; but 
+it failed to generate the proxy because the current WSDL tool does not 
+handle WSDL files that heavily use namespaces (it works with the MS.NET 
+WSDL tool).
+Here is an example of output from Apache axis:
+<?xml version="1.0" encoding="UTF-8"?>
+<wsdl:definitions xmlns="http://schemas.xmlsoap.org/wsdl/" 
+The "wsdl" namespace prefix seems to be causing the problem as it works 
+if the WSDL starts with:
+<definitions ... (without the prefix).
+Steps to reproduce the problem:
+1. Try to generate a web service proxy when Apache Axis is used for the 
+web service server.
+Actual Results:
+WSDL Tool should be able to generate a proxy.
+Expected Results:
+It should generate the proxy (as does MS.NET implementation)
+Additional Information:
+If you use the standard System.XML classes to parse the WSDL this problem 
+should go away because System.Xml provides good namespace support.
+The error:
+Error: Document element did not appear.
+in System.Xml.XmlTextReader:Read()