|
| Hello all,
I am developping a web service that runs in WASv6 WebSphere Soap engine.
It seems that constraints such as maxOccurs="1" are ignored by the SOAP engine.
Consider the following definitions:
<xs:complexType name="SomeName">
<xs:sequence>
<xs:element name="someName" type="tp:someType">
<xs:annotation>
<xs:documentation>
some doc about element 1
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:sequence>
<xs:element name="someName2" type="xs:string" minOccurs="0" maxOccurs="1"/>
<xs:element name="someName3" type="xs:string" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
</xs:sequence>
</xs:complexType>
Element someName2 and someName3 have cardinality constraints. I thought that following request would result in an error or a SoapFault because element someName2 exists two times.
<SOAP-ENV:Body>
............
<m:someName >
<m:someName2>John</m:someName2>
<m:someName2>Jim</m:someName2>
</m:someName>
.........
</SOAP-ENV:Body>
The request is processed correctly. s this a general problem or did I miss smth?
If the soap engine doesn't check, how can I do it? if I had access to the xml stream I could parse it.
Thanks in advance,
Philip
|
|