Lots of info in this thread.When I originally had this problem (at Arc 10.0), I believe it was attributed to my XML type-mapping file being in the wrong folder. The correct folder would be something like:[INDENT]C:\Program Files\Common Files\ArcGIS\Server10.2\XmlClassRegistry\YourOrganizationName\[/INDENT]The second time I had this problem (at Arc 10.1), it was related to the registering of my custom types. See NIM083300.
I am having this same problem. Can someone at ESRI comment? Who created this sample?
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
Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.