BTW,
The schema that is generated by JAXWS contains "nillable='true'", os it is ok for the client to send it ,,,
<xs:complexType name="searchCriteria">
<xs:sequence>
<xs:element name="aliases" type="tns:criteriaAlias" nillable="true" minOccurs="0" maxOccurs="unbounded"></xs:element>
<xs:element name="criterions" type="tns:criterion" nillable="true" minOccurs="0" maxOccurs="unbounded"></xs:element>
<xs:element name="numberOrItemsPerRequest" type="xs:int"></xs:element>
<xs:element name="orders" type="tns:order" nillable="true" minOccurs="0" maxOccurs="unbounded"></xs:element>
<xs:element name="requestNumber" type="xs:int"></xs:element>
<xs:element name="requireTotalRequestsCount" type="xs:boolean"></xs:element>
<xs:element name="subCriterias" type="tns:subCriteria" nillable="true" minOccurs="0" maxOccurs="unbounded"></xs:element>
<xs:element name="totalRequestCount" type="xs:int"></xs:element>
</xs:sequence>
</xs:complexType>
----- Original Message -----
From: Dima Gutzeit
To: users_at_jax-ws.dev.java.net
Sent: Monday, June 25, 2007 9:49 AM
Subject: xs:nill
Hi,
I see strange deserializing behavior in JAXWS 2.1.2.
Whenever it gets :
<aliases xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
It creates array with one null element. It is wrong :-(
Is there a way to configure this ?
Regards,
Dima Gutzeit.