Jump to content

weirriver

Members
  • Content Count

    2
  • Joined

  • Last visited

Community Reputation

0 Neutral

About weirriver

  • Rank
    Newbie
  1. weirriver

    Indicators

    I found a solution, which is to use <xs:choice maxOccurs="unbounded"/> inside of a <xs:sequence> element. I was not aware that they could be "stacked". <xs:element name="Commands"><xs:complexType><xs:sequence> <xs:choice maxOccurs="unbounded"> <xs:element name="CreateAccount" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="DeleteAccount" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="UpdateAccount" minOccurs="0" maxOccurs="unbounded" /> </xs:choice> </xs:sequence></xs:complexType></xs:element>
  2. weirriver

    Indicators

    I am using XSD to define a message structure for a service oriented architecture such that:- a message represents a command queue that can contain any number of commands in any order.- the commands are valid for the service that will process them.- each command has unique arguments and responses (i.e. there is no simple definition of a command type).Below is an excerpt from the schema with most of the grizzly details removed: <xs:element name="Commands"> <xs:complexType> <xs:choice> <xs:element name="CreateAccount" minOccurs="0" maxOccurs="unbounded" /> <xs:ele
×
×
  • Create New...