[Mono-bugs] [Bug 76808][Nor] New - Not expected behavior deserializing complex object with XmlSerializer

[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 leiszen.daniel at chello.hu.

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

--- shadow/76808	2005-11-23 20:06:50.000000000 -0500
+++ shadow/76808.tmp.26819	2005-11-23 20:06:50.000000000 -0500
@@ -0,0 +1,33 @@
+Bug#: 76808
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: Microsoft Windows XP SP2
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Sys.XML
+AssignedTo: atsushi at ximian.com                            
+ReportedBy: leiszen.daniel at chello.hu               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Not expected behavior deserializing complex object with XmlSerializer
+
+The result of deserializing a complex object by
+System.Xml.Serialization.XmlSerialzer is differs in Mono 1.1 from
+Microsoft.NET Framework 1.1.
+
+Description of Problem:
+
+The concrete situation is, to serialize and deserialize a complex type
+which implements a simple hierarchical tree. Every node in the tree has a
+collection as its children. When a new node is added to the collection, a
+reference for the parent node must be set. Therefore the collection must
+notify the parent to set the newly added node, or the collection must know
+its conainer (the parent node) and set every child node during addition.
+
+Under Microsoft.NET 1.1 every kind of implementation works. When I run the
+application with Mono 1.1 the deserializer does not build the correct tree.