Server Object Extension (SOE) - XmlClassRegistry Files Not Used?

Discussion created by ebrimhall on Jan 11, 2011
Latest reply on Feb 5, 2014 by MikeEber
I have followed the basic example for creating a SOAP Server Object Extension (SOE) using the walkthrough provided by ESRI, but have encountered a problem:

[INDENT]It appears that ArcGIS Server is not looking in the "XmlClassRegistry" folder/sub-folders for files defining mappings between custom XML and COM-visible types.

The effect is that any attempt to deserialize an XML type as its corresponding COM class fails with "Exception from HRESULT: 0x80043068" (XML_SERIALIZE_E_CANT_MAP_XMLTYPE_TO_CLASS).

If the custom XML/COM type mapping definitions are moved to the "XmlSupport.dat" that ArcGIS Server uses to map ESRI types, then the custom types can be correctly deserialized.

Is there a defect in ArcGIS Server related to custom type deserialization, or is the SOAP SOE walkthrough incomplete in this regard?

Any help would be greatly appreciated!