[Mono-bugs] [Bug 77907][Nor] New - [PATCH] XmlSchemaImporter.ImportTypeMapping loses TypeData for primitive types

[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 gert.driesen at pandora.be.

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

--- shadow/77907	2006-03-25 04:05:00.000000000 -0500
+++ shadow/77907.tmp.8786	2006-03-25 04:05:00.000000000 -0500
@@ -0,0 +1,32 @@
+Bug#: 77907
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: Sys.XML
+AssignedTo: lluis at ximian.com                            
+ReportedBy: gert.driesen at pandora.be               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: [PATCH] XmlSchemaImporter.ImportTypeMapping loses TypeData for primitive types
+
+For primitive types, XmlSchemaImporter.ImportTypeMapping passes the 
+TypeData.Type to XmlReflectionImporter and SoapReflectionImporter, and 
+therefore we always end up losing any specific information in TypeData 
+(such as ElementName).
+
+For example, by importing this:
+
+<xs:element name=\"date\" type=\"xs:date\" />
+
+you end with a TypeData that has ElementName set to "date", but if you 
+only pass TypeData.Type to, for example, XmlReflectionImporter then you 
+always end with the hashtable entry in TypeTranslators.nameCache for that 
+type, and a such you lose the specific information of the imported 
+element.