[Mono-bugs] [Bug 63828][Min] Changed - System.Web.UI.WebControls.Xml

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 24 Aug 2004 18:27:01 -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 bugzilla@thetoxiczone.com.


--- shadow/63828	2004-08-24 16:03:24.000000000 -0400
+++ shadow/63828.tmp.9734	2004-08-24 18:27:01.000000000 -0400
@@ -2,13 +2,13 @@
 Product: Mono: Class Libraries
 Version: unspecified
 OS: SUSE 9.1
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Minor
 Component: Sys.Web
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: bugzilla@thetoxiczone.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -105,6 +105,33 @@
 ------- Additional Comments From bugzilla@thetoxiczone.com  2004-08-24 16:03 -------
 Created an attachment (id=9480)
 Actual Result
+------- Additional Comments From bugzilla@thetoxiczone.com  2004-08-24 18:27 -------
+This appears to be the same as bug #62726 (found when looking in CVS 
+to test my fix idea sorry about the duplicate, my initial pre-
+submission search did not show this), however I have now looked at 
+the new source code for this fix (CVS revision 1.17) I feel that 
+this fix will not fully fix the file mapping and will have 
+introduced a new bug as well.
+I will explain the new bug as best I can.
+In method the LoadXpathDoc if documentContent has data it will 
+attempt to map this as a path but this field is not for a file path 
+it is for raw xml text, see LoadXmlDoc where it is used in a LoadXml.
+I will attach a new test case page that should flag this issue, and 
+produce the same expected result as my other test case, not sure 
+what the actual result will be, as I have not got round to setting 
+up to build things yet.
+The second mapping issue will get flagged when somebody reads the 
+Document property if they just set the DocumentSource property as 
+this will call LoadXmlDoc.  I might be able to come up with a test 
+case for this if needed.
+While trying to get a feel for the code here and to avoid stepping 
+on other fixes it looks like this issue is due to bug #55334 that 
+was just invalid parameters.