|
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 |
- Re: Returning nulls with minOccurs set to 0 Eugene Shershnev
- Re: Returning nulls with minOccurs set to 0 Eugene Shershnev
- RE: Returning nulls with minOccurs set to 0 Simon Fell
- Re: Returning nulls with minOccurs set to 0 Eugene Shershnev
- Re: Returning nulls with minOccurs set to 0 Eugene Shershnev
