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

[ErinBrimhall]

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.
[/INDENT]



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!

Thanks

[MichaelEber]

I am just falling into the deep hole of SOE deployment.

I went through the example and found that the code is not for 10.1.  First I got somewhere around 20 build failures when trying to build the example.  Second it says to use RegAsm but ESRI documentation in another area now says stop using that and use ESRIRegAsm which goes back to 9.3.1.  That should give you a taste for how old that example is. 

LOL the only documentation that appears to be decent and it is useless for the current software.