[AXIS-1357] non nillable element sent as nil

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2 Beta
• Fix Version/s: 1.2
• Component/s: Serialization/Deserialization, WSDL processing
• Environment: Win 2k, Resin
• Assignee: Unassigned
• Reporter: Brian Speight
• Created: 11/May/04 18:57
• Updated: 27/Sep/06 00:45
• Resolved: 18/Nov/04 17:07

Description

Element defined in schema:

<element name="numberOfChildren" type="xsd:int" minOccurs="0"/>

When using Axis 1.2 Alpha:

wsdl2java generates this...
private int numberOfChildren;

and when not setting any value for this, this is what is sent in the SOAP request...

<numberOfChildren href="#id3"/>
<multiRef id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="xsd:int" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">0</multiRef>

So this works as expected.

But, when using Axis 1.2 Beta:

wsdl2jav generates this...
private java.lang.Integer numberOfChildren;

and when not setting any value for this, this is what is sent in the SOAP request...

<numberOfChildren xsi:type="xsd:int" xsi:nil="true"/>

This element was not declared as nillable in the schema and when sent as nil blows up when trying to deserialize.

Issue Links

• duplicates: AXIS-530 elements without minOccurs="0" produce isnill="true" on the wire