wiki:DX/SimpleWSDLContainerXML

Version 7 (modified by spascoe, 13 years ago) (diff)

--

Defining a simple container WSDL for DX request-response

Purpose

The purpose of this page is to look at how we could quickly define a container schema for the DX WSDL that would essentially allow us to package arbitrary stuff into an XML container with a set WSDL, rather than with the existing non-WSDL list of lists approach.

This in no ways aims to be OGC-compliant. It would only serve as a temporary definition to expose the DX with a proper WSDL rather than limiting letting ZSI generate the Web-Service Interface internally. That would make it plug and play better with other clients.

First Bash

Below is first bash of an XML stub for a DX request:

<dxRequest>
    <sessionID/>
    <secureToken/>
    <argumentList>
        <arg>
            <argName>
            <argType>
            <argValue>
        </arg>
    </argumentList>
</dxRequest>

Then this is a possible DX response doc:

<dxResponse>
    <sessionID/>
    <secureToken/>
    <returnCode/>
    <infoMessage/>
    <optionList>
        <opt>
            <optionName/>
            <optionType/>
            <optionValue/>
        </opt>
    </optionList>
</dxResponse>

Suggestion (StephenPascoe?)

If we can define our XML schema as we wish I tend to prefer minimising nesting. Something like this looks more concise to me.

<dxRequest>
  <sessionID>...</sessionID>
  <secureToken>...</secureToken>
  <arg name="..." type="...">...value...</arg>
  ...more args...
</dxRequest>

<dxResponse>
  <sessionID>...</sessionID>
  <secureToken>...</secureToken>
  <returnCode>...</returnCode>
  <infoMessage>...</infoMessage>
  <opt name="..." type="...">...value...</opt>
  ...more opts...
</dxResponse>

Is there any reason why this couldn't be defined in an XML-schema/WSDL and used inside doc-literal SOAP?