DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14902>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14902 elements without minOccurs="0" produce isnill="true" on the wire ------- Additional Comments From [EMAIL PROTECTED] 2002-12-11 17:26 ------- Here is a full test of nimOccurs/maxOccurs/nillable for a null class field / serializable element, with on the wire results for Axis 1.0 and .NET: <element name="t0" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="false"/> dotNet="" Axis="" <element name="t1" type="xsd:string" minOccurs="0" maxOccurs="1" nillable="true"/> dotNet="<t1 xsi:nil="true" />" Axis="" <element name="t2" type="xsd:string" minOccurs="0" maxOccurs="unbounded" nillable="false"/> dotNet="" Axis="" <element name="t3" type="xsd:string" minOccurs="0" maxOccurs="unbounded" nillable="true"/> dotNet="" Axis="" <element name="t4" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="false"/> dotNet="" Axis="<t4 xsi:nil="true"/>" <element name="t5" type="xsd:string" minOccurs="1" maxOccurs="1" nillable="true"/> dotNet="<t5 xsi:nil="true" />" Axis="<t5 xsi:nil="true"/>" <element name="t6" type="xsd:string" minOccurs="1" maxOccurs="unbounded" nillable="false"/> dotNet="" Axis="" <element name="t7" type="xsd:string" minOccurs="1" maxOccurs="unbounded" nillable="true"/> dotNet="" Axis="" t4 and t7 should throw an Exception as minOccurs="1" and the element is not nillable. t1 can be debated and should be reviewed as the element could be sent as <t1 xsi:nil="true"/>.
