Shared value objects

ArcGIS Server Web services share many base value object types since they share similar input and output type requirements.  For example, all ArcGIS Server Web service WSDLs define the same set of geometry types since all ArcGIS Server Web service utilize geometry.   Types defined via XML in a WSDL become value objects when consumed by a client using a SOAP toolkit.  SOAP tookits are designed for specific development environments, so a toolkit for .NET will generate native .NET value objects and Web service proxy classes for use within a .NET application.   In most development environments, the SOAP toolkit will define a namespace for the value objects and proxies.   As a result, value object properties and input parameters and output results for proxy methods must share the same namespace to be used together.  For compiled languages, such as C#, VB.NET, and Java, all value objects and Web service proxies that are used together must share the same namespace, otherwise it will not compile.    Fortunately, SOAP toolkits usually provide the ability to generate value objects and proxies from multiple WSDLs at the same time within the same namespace.  In the process, value object types shared between the WSDL definitions will only be created once and be available for use with all proxy methods and other value object properties.  Tutorials illustrating the generation of shared types are available for the development environments listed below.
 

If you have complete control over the generation of SOAP proxies and value objects, you can generate value object types that can be shared across ArcGIS Server service types.   If you are unable to modify the namespace for SOAP proxies and value objects, you may be able to convert between namespaces.  Use the following code examples.