[Mono-bugs] [Bug 61464][Cos] Changed - MS XmlSerializer can serialize ArrayList derived class with no public parameterless constructor, while Mono implementation cannot

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 15 Jul 2004 12:49:27 -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 lluis@ximian.com.


--- shadow/61464	2004-07-15 11:20:15.000000000 -0400
+++ shadow/61464.tmp.12543	2004-07-15 12:49:27.000000000 -0400
@@ -1,12 +1,12 @@
 Bug#: 61464
 Product: Mono: Class Libraries
 Version: unspecified
 OS: All
 OS Details: Gentoo linux
-Status: NEEDINFO   
+Status: REOPENED   
 Severity: Unknown
 Priority: Cosmetic
 Component: Sys.XML
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: psonek2@seznam.cz               
@@ -110,6 +110,20 @@
 serialize/de-serialize. Please show the saved xml, for a better diagnosis.
+------- Additional Comments From lluis@ximian.com  2004-07-15 12:49 -------
+Rafael, some corrections: the XmlSerializer in Whidbey can't access
+private members, just like in .NET 1.1. The serializer in .NET 2.0 is
+the same, with some minor changes. Indigo will introduce a new
+serializer which supports private members, but this is not par of Whidbey.
+This test case works in MS.NET as far as the MyList instance is
+created by it's container. If the field is null, it will also fail
+since the serializer can't use a public constructor to create the
+list. In mono we check that all classes are public when construction
+the xml mappings, and we are not considering this scenario. We just
+need to change this.