W3C home > Mailing lists > Public > public-xsd-databinding@w3.org > July 2006

ISSUE-15: emptySequence pattern

From: <paul.downey@bt.com>
Date: Sun, 16 Jul 2006 23:41:19 +0100
Message-ID: <2A7793353757DB4392DF4DFBBC95225504BFEBA1@I2KM11-UKBR.domain1.systemhost.net>
To: <edday@obj-sys.com>, <public-xsd-databinding@w3.org>

I've encountered :

<xs:element name="emptyResponse">
   <xs:complexType>
     <xs:sequence/>
   </xs:complexType>
</xs:element>

in some WSDLs for an empty/null response message
element. .NET and others generate a method 
returning void.

So have contributed the examples:

   <e:example xml:id="EmptySequence" element="emptySequence">
      <e:typedef>
        <xs:element name="emptySequence">
           <xs:complexType>
             <xs:sequence/>
           </xs:complexType>
        </xs:element>
      </e:typedef>
      <e:instance xml:id="emptySequence01">
         <ex:emptySequence/>
      </e:instance>
   </e:example>

to accompany the other two from Ed:

    <e:example xml:id="NullEnumeration" element="nullEnumeration">
      <e:typedef>
        <xs:element name="NullEnumeration" type="ex:NullEnumeration"/>
        <xs:simpleType name='NullEnumeration'>
          <xs:restriction base='xs:string'>
             <xs:enumeration value=''/>
          </xs:restriction>
        </xs:simpleType>
      </e:typedef>
      <e:instance xml:id="nullEnumeration01">
         <ex:nullEnumeration/>
      </e:instance>
   </e:example>

   <e:example xml:id="EmptyComplexType" element="emptyComplexType">
      <e:typedef>
        <xs:element name="emptyComplextType">
           <xs:complexType/>
        </xs:element>
      </e:typedef>
      <e:instance xml:id="emptyComplexType01">
         <ex:emptyComplexType/>
      </e:instance>
   </e:example>


see http://www.w3.org/2002/ws/databinding/examples/6/05/#NullEnumeration
Received on Sunday, 16 July 2006 22:41:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 18:20:37 GMT