[Mono-bugs] [Bug 57413][Maj] Changed - problem in DataSet Deserialization.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 22 Apr 2004 10:34:57 -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 atsushi@ximian.com.


--- shadow/57413	2004-04-22 10:08:42.000000000 -0400
+++ shadow/57413.tmp.11532	2004-04-22 10:34:57.000000000 -0400
@@ -2,16 +2,16 @@
 Product: Mono: Class Libraries
 Version: unspecified
 OS: All
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Major
 Component: Sys.XML
-AssignedTo: atsushi@ximian.com                            
+AssignedTo: lluis@ximian.com                            
 ReportedBy: along@mainsoft.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 Summary: problem in DataSet Deserialization.
@@ -45,6 +45,20 @@
 ------- Additional Comments From atsushi@ximian.com  2004-04-22 10:08 -------
 Created an attachment (id=7462)
 Proposed patch (In some cases, DataSet.ReadXml() consumes EndElement)
+------- Additional Comments From atsushi@ximian.com  2004-04-22 10:34 -------
+Additional comments:
+> In some cases, DataSet.ReadXml() consumes EndElement
+It is not because of unintended implementation changes. If interested,
+you can check some tests in DataSetXmlReadTest.cs (in System.Data)
+that checks if argument XmlReader is consumed to the end.
+Also, in case of custom IXmlSerializable classes, we cannot depend on
+that XmlReader always ends with EndElement status.
+Reassigning to lluis ;-)