Hi Franz,
While I did not specifically test for that scenario, I believe the
solution will work. The tests I put in tests the following type coming in
as start/end element:
<s:complexType name="ArrayOfInfoString">
<s:attribute name="attributeA" type="s:string" use="optional"/>
<s:attribute name="attributeB" type="s:string" use="required"/>
<s:sequence>
<s:element minOccurs="0" maxOccurs="unbounded" name="InfoString"
nillable="true">
<s:complexType name="InfoString">
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="CodInfoString"
type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
And I see no reason why any number of optional elements would not work.
All optional element processing does a peek(), so peek will return NULL
string no matter the number of optional elements.
Nadir K. Amra
Franz Fehringer <[EMAIL PROTECTED]> wrote on 01/15/2007 04:49:51 AM:
> Hallo Nadir,
>
> Does the checked in fix correctly handle the case
> <mytag mykey="myvalue"/>
> where *two* (or more) optional elements are missing.
> I was slightly concerned about this case(s) with my solution.
>
> Cheers
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
