Hi,

I need clarification regarding xsd:all. As per the specification,

If the {compositor} is all, then there must be a ·partition· of the
sequence into n sub-sequences where n is the length of {particles} such
that there is a one-to-one mapping between the sub-sequences and the
{particles} where each sub-sequence is ·valid· with respect to the
corresponding particle as defined in Element Sequence Locally Valid
(Particle) (§3.9.4).

Does it mean, for the following wsdl snippet wherein there are 3 particles
of different types, Axis C++ *must* be able to generate three sub sequences
of SOAP request messages randomly as mentioned below or will it generate
only one sequence of SOAP message ?
|-----------------+-----------------+-----------------+-----------------|
|xsd:all          |                 |                 |                 |
|-----------------+-----------------+-----------------+-----------------|
|WSDL snippet     |   Sample SOAP   |                 |                 |
|                 |message snippets |                 |                 |
|-----------------+-----------------+-----------------+-----------------|
|<xsd:element name|<                |<                |<                |
|=                |ExampleOperationR|ExampleOperationR|ExampleOperationR|
|"ExampleOperation|equest>          |equest>          |equest>          |
|Request">        |  <IntElement>   |  <StringElement>|  <IntElement>   |
|  <              |12345</IntElement|string</         |12345</IntElement|
|xsd:complexType> |>                |StringElement>   |>                |
|    <xsd:all>    |  <StringElement>|  <DateElement>  |  <DateElement>  |
|      <          |string</         |2004-11-12Z</    |2004-11-12Z</    |
|xsd:element name=|StringElement>   |DateElement>     |DateElement>     |
|"IntElement"     |  <DateElement>  |  <IntElement>   |  <StringElement>|
|        type=    |2004-11-12Z</    |12345</IntElement|string</         |
|"xsd:integer />  |DateElement>     |>                |StringElement>   |
|      <          |</               |</               |</               |
|xsd:element name=|ExampleOperationR|ExampleOperationR|ExampleOperationR|
|"StringElement"  |equest>          |equest>          |equest>          |
|        type=    |                 |                 |                 |
|"xsd:string" />  |                 |                 |                 |
|      <          |                 |                 |                 |
|xsd:element name=|                 |                 |                 |
|"DateElement"    |                 |                 |                 |
|        type=    |                 |                 |                 |
|"xsd:date" />    |                 |                 |                 |
|    </xsd:all>   |                 |                 |                 |
|  </             |                 |                 |                 |
|xsd:complexType> |                 |                 |                 |
|</xsd:element>   |                 |                 |                 |
|-----------------+-----------------+-----------------+-----------------|




If Axis C++ is supposed to generate three sub sequences of SOAP request
messages how to influence SOAP engine to do the same ?

Regards
Manohar

Reply via email to