W3C home > Mailing lists > Public > www-ws@w3.org > August 2001

Re: WSDL and HTTP GET

From: Jeff Lansing <jeff@polexis.com>
Date: Thu, 30 Aug 2001 08:56:18 -0700
Message-ID: <3B8E6221.A218213E@polexis.com>
CC: "'www-ws@w3.org'" <www-ws@w3.org>
Hi Markus,

I think the problem with your suggestion is that it would allow a WSDL enabled
client to generate requests like the following:

http://www.example.org/cgi-bin/service.cgi?VERSION=&REQUEST=GetQuote

which of course is invalid URL syntax. It seems like we have to do more, that
there has to be some convention established for using types containing multiole
optional elements. I suggest the following:
  <types>
    <schema>
      <complexType name="someType">
        <group ref="someGroup"/>
      </complexType>
      <group name="someGroup">
        <all>
          <element ref="VERSION" minOccurs="0"/>
          <element ref="REQUEST"/>
        </all>
      </group>
      <element name="VERSION" type="simpleType1"/>
      <element name="REQUEST" type="simpleType2"/>
    </schema>
  </types>

  <message...>
    <part name="HttpGETRequest" type="someType"/>
  </message>

Regards,

Jeff


"Kinateder, Markus" wrote:

> Hello Jeff,
>
> as you said:
>
> "...the string content of an element of the required type is a valid value
> for the corresponding HTTP GET parameter."
>
> So maybe constructions like that would be possible:
>
> <types>
>   <schema>
>     <complexType name="versionType">
>       <all>
>         <element name="someElement" type="simpleType1" minOccurs="0"/>
>       </all>
>     </complexType>
>     <complexType name="requestType">
>       <all>
>         <element name="someElement" type="simpleType2"/>
>       </all>
>     </complexType>    <!-- further type definitions -->
>   </schema>
> </types>
>
> <message...>
>   <part name="VERSION" type="versionType"/>
>   <part name="REQUEST" type="requestType"/>
> </message>
>
> Valid elements of the defined types (in XML representation) would look like:
>
> <VERSION>
>   <someElement>1.1</someElement>
> </VERSION>
>
> or
>
> <VERSION/>
>
> and
>
> <REQUEST>
>   <someElement>GetQuote</someElement>
> </REQUEST>
>
> The string content of those elements is "1.1", "" and "GetQuote",
> respectively. As you said, this gives valid values for the HTTP GET
> parameters.
>
> In this picture the type of a HTTP GET-Parameter would be the concatenation
> of all "TextNode-Types" contained within the element- or type-definition
> referenced in the message part. The name of the HTTP GET-Parameter still
> could remain the name of the message part.
>
> Best regards,
>
> Markus
Received on Thursday, 30 August 2001 11:56:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:38 GMT