On Tue, 04 Apr 2006 07:02:40 +0600, in soap you wrote:
On Mon, 2006-04-03 at 13:10 -0700, Simon Fell wrote:
Please don't do this, if the schema says
<complexType>
<element name="foo" type="xsd:string"/>
<element name="bar" minOccurs="0" maxOccurs="unbounded" nilable="true"/>
</complexType>
then
<x>
<foo>a</foo>
<bar xsi:nil='true'/>
</x>
Means something completely different to
<x>
<foo>a</foo>
</x>
True. What do you suggest we do for zero length arrays where we don't
have the schema around? The only think I can think of is for the pull
parser to have two modes .. and for the one who calls it to know what to
do. That way in an ADB generated case where the generated code knows the
right thing to do it can call the appropriate form of zero length array
serialization.
Sanjiva.
Unless you're doing .NET ass funky array wrapping (in which case you
deserve everything you get), a 0 zero length array should serialize no
elements.
Which is exactly what my patch does, now attached to both this issue
http://issues.apache.org/jira/browse/AXIS2-520 and issue 523
http://issues.apache.org/jira/browse/AXIS2-523
Chuck
|
