[Mono-bugs] [Bug 75581][Nor] Changed - Soap serialization interop

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Jul 19 06:08:06 EDT 2005

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 roeie at mainsoft.com.


--- shadow/75581	2005-07-19 05:04:32.000000000 -0400
+++ shadow/75581.tmp.25516	2005-07-19 06:08:06.000000000 -0400
@@ -0,0 +1,57 @@
+Bug#: 75581
+Product: Mono: Class Libraries
+Version: 1.1
+OS: unknown
+OS Details: 
+Status: RESOLVED   
+Resolution: NOTABUG
+Severity: Unknown
+Priority: Normal
+Component: CORLIB
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: roeie at mainsoft.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Soap serialization interop
+Description of Problem:
+When serializing an object using SoapFormatter, the soap message starts 
+with the full qualified name of the type of the serialized object, and 
+the full qualified name of its assembly.
+on MS.NET platform the assmebly part is removed when the type is taken 
+from one of the .NET runtime libaries (like System.Web.dll, 
+on MONO platfrom the assembly part is only removed if the type is taken 
+from the mscorlib.dll.
+I belieave that the reason for this behaviour int MS.NET is for version 
+Steps to reproduce the problem:
+serialize a serializable type from one of the .NET runtime libaries on 
+MONO platform and on MS.NET platform, and see the difference
+Actual Results:
+ difference in encoding the type name
+Expected Results:
+ should be the same
+How often does this happen? 
+every time
+Additional Information:
+------- Additional Comments From roeie at mainsoft.com  2005-07-19 05:04 -------
+The problem is in the class SoapTypeMapper at the indexer: 
+public Element this[string typeFullName, string assemblyName].
+There is a check there only for mscorlib types and not for 
+other .net assemblies types.
+------- Additional Comments From roeie at mainsoft.com  2005-07-19 06:08 -------
+After rechecking it with MS.NET it appers to be my mistake, igonre 
+this bug

More information about the mono-bugs mailing list