[Mono-bugs] [Bug 82401][Nor] New - Remoting serialization problem with array of arrays

[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 jaebird at gmail.com.

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

--- shadow/82401	2007-08-10 14:55:55.000000000 -0400
+++ shadow/82401.tmp.32050	2007-08-10 14:55:55.000000000 -0400
@@ -0,0 +1,87 @@
+Bug#: 82401
+Product: Mono: Class Libraries
+Version: 1.2
+OS: GNU/Linux [Other]
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: jaebird at gmail.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Remoting serialization problem with array of arrays
+
+Description of Problem:
+We are passing array of array of our custom object (ie not framework) as a
+parameter to remote methods. This works fine between to .NET boxes or if
+the server is running on mono (linux), but fails if one of the server is
+running on windows and client on mono (linux). We are actually using
+interfaces, but the behavior is the same. 
+
+Example:
+
+Client:
+HappyHello[][] hello = ....
+testRemoteMethod.Hello(hello);
+
+
+Actual Results:
+The exception that is returned is a rethrown exception (coming from the
+server) as a serialization error:
+
+  at
+System.Runtime.Serialization.Formatters.Binary.ObjectWriter.GetAssemblyNameId
+(System.String assembly) [0x00000]
+  at
+System.Runtime.Serialization.Formatters.Binary.ObjectWriter.GetAssemblyId
+(System.Reflection.Assembly assembly) [0x00000]
+  at
+System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteTypeSpec
+(System.IO.BinaryWriter writer, System.Type type) [0x00000]
+  at
+System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteGenericArray
+(System.IO.BinaryWriter writer, Int64 id, System.Array array) [0x00000]
+  at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteArray
+(System.IO.BinaryWriter writer, Int64 id, System.Array array) [0x00000]
+  at
+System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteObjectInstance
+(System.IO.BinaryWriter writer, System.Object obj, Boolean isValueObject)
+[0x00000]
+  at
+System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteQueuedObjects
+(System.IO.BinaryWriter writer) [0x00000]
+  at
+System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteObjectGraph
+(System.IO.BinaryWriter writer, System.Object obj,
+System.Runtime.Remoting.Messaging.Header[] headers) [0x00000]
+  at
+System.Runtime.Serialization.Formatters.Binary.MessageFormatter.WriteMethodCall
+(System.IO.BinaryWriter writer, System.Object obj,
+System.Runtime.Remoting.Messaging.Header[] headers, ISurrogateSelector
+surrogateSelector, StreamingContext context, FormatterAssemblyStyle
+assemblyFormat, FormatterTypeStyle typeFormat) [0x00000]
+  at
+System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize
+(System.IO.Stream serializationStream, System.Object graph,
+System.Runtime.Remoting.Messaging.Header[] headers) [0x00000]
+  at
+System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage
+(IMessage msg) [0x00000] 
+
+Expected Results:
+Object to be passed over successfully
+
+How often does this happen? 
+Every time
+
+Additional Information:
+The client is not serializing the object[][] properly which causes the
+server to throw the exception. Like I mentioned above, if the server is
+running on mono, the windows client serializes properly and the server does
+not throw and error. Also, if I change it to only be one array of
+HappyHello, the code works fine on both platforms.