[Mono-bugs] [Bug 80120][Nor] Changed - wsdl tool can not import MSDN wsdl

[bugzilla-daemon at bugzilla.ximian.com]

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 atsushi at ximian.com.

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

--- shadow/80120	2006-12-01 11:40:16.000000000 -0500
+++ shadow/80120.tmp.3416	2006-12-11 03:31:10.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 80120
 Product: Mono: Class Libraries
 Version: 1.2
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: Sys.Web.Services
 AssignedTo: atsushi at ximian.com                            
 ReportedBy: miguel at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -51,6 +51,29 @@
   at Mono.WebServices.Driver.GenerateCode
 (System.Web.Services.Description.WebReferenceCollection references,
 System.CodeDom.CodeCompileUnit codeUnit) [0x00000]
   at Mono.WebServices.Driver.Run (System.String[] args) [0x00000]
 
 This wsdl works with .NET 2.0, but fails with .NET 1.1
+
+------- Additional Comments From atsushi at ximian.com  2006-12-11 03:31 -------
+Three issues were involved.
+- ProtocolImporter incorrectly expected XmlSchemaImport in a foreach()
+where XmlSchemaInclude or XmlSchemaRedefine could appear.
+- There is an ID conflict in the schemas used in the WSDL. This is
+_likely_ Microsoft bug in that WSDL (schema set), as well as .NET 2.0
+System.Xml (since .NET 2.0 allows that WSDL).
+- ServiceDescription incorrectly expected
+ServiceDescriptionFormatExtension in a foreach() where XmlElement
+could appear.
+
+The second issue is more complicated. XML Schema Datatypes does *not*
+define xs:ID type as to be identical in the whole schema scope
+(XmlSchemaSet in .net land). Hence IDs should be only identical in a
+document. However many Microsoft tests in W3C Xml Schema Test
+Collection require such identity, while at least some (e.g.
+ctA029.xsd) schemas only check id validity on schema components
+themselves. Since .NET still checks those ids but not for xs:schema,
+.NET is likely to have an inconsistency (bug) there.
+
+I will close this bug when my changes to Sys.Web.Services that are
+already in my branch are merged into trunk.