[Mono-bugs] [Bug 72739][Nor] Changed - XmlSerializer will serialize invalid XML characters but complain at deserialization.

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 25 Feb 2005 14:37:54 -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 joeshaw@novell.com.

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

--- shadow/72739	2005-02-25 11:27:13.000000000 -0500
+++ shadow/72739.tmp.1659	2005-02-25 14:37:54.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 72739
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: RESOLVED   
-Resolution: NOTABUG
+Status: REOPENED   
+Resolution: 
 Severity: Unknown
 Priority: Normal
 Component: Sys.XML
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: joeshaw@novell.com               
 QAContact: mono-bugs@ximian.com
@@ -31,6 +31,16 @@
 
 ------- Additional Comments From lluis@ximian.com  2005-02-25 11:27 -------
 I'm resolving this as NOTABUG because MS.NET behaves in the same way.
 In .NET 1.1 there is no way to load a document with invalid chars,
 although in 2.0 there is an option in XmlReaderSettings to disable
 this check.
+
+------- Additional Comments From joeshaw@novell.com  2005-02-25 14:37 -------
+Perhaps I wasn't being clear, or I don't totally understand your answer.
+
+I have no problem with it not deserializing and loading invalid XML
+off the wire, that's fine.  But (without having checked whether MS
+.NET does this) it does seem like a bug that it will serialize and put
+invalid XML on the wire.  XmlSerializer will create an invalid
+document if its input has an invalid character, rather than either
+removing it or throwing an exception.