I have a WSDL-file that looks like the following (Part of it)

- <s:complexType name="Persoonslijst">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Persoon"
type="s0:CAT01type" />
</s:sequence>
</s:complexType>

- <s:complexType name="CAT01type">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Geboorte"
type="s0:GR03type" />
</s:sequence>
</s:complexType>

- <s:complexType name="GR03type">
- <s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="Geboortedatum"
type="s:unsignedInt" />
<s:element minOccurs="0" maxOccurs="1" name="Geboorteplaats"
type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Geboorteland"
type="s:integer" />
</s:sequence>
</s:complexType>

-------------------------------------------------------------------------

I have a XMLDataDocument where I have specified a node
[Geboortedatum].
As long as it has a value like

<Persoonslijst>
<Persoon>
<Geboortedatum>19800305</Geboortedatum>
</Persoon>
</Persoonslijst

Deserialization works fine.

But when the <Geboortedatum> is empty like <Geboortedatum />,
deserialization fails.

Question...

In my first WSDL the value of minoccurs of Geboortedatum was set to 1
In my last WSDL i set the minoccurs to 0, expecting (and hoping!) that
it was possible to leave the Geboortedatum node empty. But this fails.

I'm expecting now that because the type = unsignedInt, it validates
the value I'm want to deserialize against this type. And a value of
empty is not valid.
(We I change the type from unsignedInt to string, there is no problem)

So can anyone please tell me what the true story is.

Kind regards Patrick