The XML instance document you supplied doesn't match the WSDL schema, so
Axis is correct in rejecting it. You should just have minOccurs="0"
added to the schema for the element. There's no reason to add
nillable="true", since just leaving the element out is the cleaner approach.
How did the th
Anne,
Yes, I came to the conclusion there was a difference, but I added both
purely to try and persuade Axis to handle the error.
I think Axis is ignoring the minOccurs="0", despite the fact I can see it
being set up in the source code generated:
elemField = new org.apache.axis.descript
John,
There's a difference between missing and null. If the element had a
null value, then the element would be there, and it would say
.
If the schema says minOccurs="0", then this message is valid.
It appears that Axis is not properly handling minOccurs="0".
Anne
On 8/5/05, John Baker <[EMAI
Hi,
I am using a WSDL file supplied to be by a third party and I suspect it
doesn't quite reflect what their .NET server is returning in the SOAP
messages. I am getting this exception:
java.io.IOException: Non nillable element 'requestCategoryCode' is null.
at
org.apache.axis.encoding.ser
