[Mono-bugs] [Bug 79924][Nor] Changed - [TEST] nant enters endless loop on mono >= 1.1.17

[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 gert.driesen at pandora.be.

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

--- shadow/79924	2006-11-14 10:04:15.000000000 -0500
+++ shadow/79924.tmp.8892	2006-11-15 16:37:27.000000000 -0500
@@ -50,6 +50,34 @@
 
 ------- Additional Comments From gert.driesen at pandora.be  2006-11-14 09:17 -------
 I'll first have a look, before bothering Atsushi with this.
 
 ------- Additional Comments From atsushi at ximian.com  2006-11-14 10:04 -------
 Thanks Gert.
+
+------- Additional Comments From gert.driesen at pandora.be  2006-11-15 16:37 -------
+Atsushi, (as I mentioned on IRC) I cannot reproduce the endless loop 
+in NAnt.
+
+What I did notice is that Mono performs XML Schema validation in 
+XmlDocument.Load(string) if xsi:noNamespaceSchemaLocation is set in 
+the XML instance, while MS does not.
+
+I've attached a (gzipped) tar archive containing a small repro.
+
+To reproduce:
+
+1. extract the tar.
+2. compile test.cs
+3. run it with the following arguments:
+* input1.xml : on MS you get no XmlSchemaException although the 
+referenced XML Schema is not valid
+* input2.xml : the host specified in noNamespaceSchemaLocation is 
+not reachable. This causes a substantial delay on Mono, but no delay 
+at all on MS.
+
+This makes me think that MS does not even fetch the XML Schema (let 
+alone validate). I could be totally wrong ofcourse.
+
+About Leslek's issue: perhaps he did not have internet connectivity 
+on his system or sf.net (where the NAnt xsd is hosted) was extremely 
+slow (isn't always?), which would explain the long delay.