|
As you say it doesn't cause a problem for strings, but if
that was an int or date, then it would cause the .NET client to be unable to
parse the message. I think there was a post RC3 fix for this, have you tried the
latest code ?
Cheers
Simon
Hi All,
I have a simple test to check the interop issues between
Axis 1.2 RC3 server and .Net client.
A function returns a String so the element in the WSDL
is defined as follows:
<element name="nullableStringOutResponse">
<complexType>
<sequence>
<element
name="nullableStringOutReturn" nillable="true" minOccurs="0"
type="xsd:string"/>
</sequence>
</complexType>
</element>
and when that function returns null the response looks like
this:
<soapenv:Body>
<nullableStringOutResponse
xmlns="http://test.enterprise.ent">
<nullableStringOutReturn xsi:nil="true"/>
</nullableStringOutResponse>
</soapenv:Body>
What I was actually expecting is:
With minOccurs="0" there is no need for Axis to serialize a
null string as it does.
This does not cause any problem (at least in my case), but
why send any extra bytes when they're not required?
Thanks,
Eugene
|
