While I'm loathe to make changes in our code to accomodate bugs in other
vendors tools, this sounds reasonable.
- James Snell
IBM Emerging Technologies
[EMAIL PROTECTED]
(559) 587-1233 (office)
(700) 544-9035 (t/l)
Programming Web Services With SOAP
O'Reilly & Associates, ISBN 0596000952
Have I not commanded you? Be strong and courageous.
Do not be terrified, do not be discouraged, for the Lord your
God will be with you whereever you go. - Joshua 1:9
David Marquard <[EMAIL PROTECTED]>
02/19/2003 02:46 PM
Please respond to axis-dev
To
"'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc
bcc
Subject
Request that zero length array interop patch be applied in time f or
1.1 final
I'd like to request that the patch in bug #17021
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17021) be applied in
time
for the 1.1 final release.
Currently, .Net 1.0 clients cannot deserialize objects from axis that
contain zero length arrays due to a bug in Microsoft's deserializer.
Basically, .Net 1.0's deserializer goes belly up if a zero length array
doesn't have an explicit closing tag (i.e., <myArray/> fails, but
<myArray></myArray> works).
The patch adds a new configuration option to axis called
"sendMinimizedElements", which when set to "false" causes axis to always
send explicit closing tags for empty elements. This cleanly works around
the
Microsoft bug, but does not sacrafice axis's correctness. The default
value
of the new option is "true", which does not change axis's current
behavior.
The patch is extremely small (< 20 lines changed) and simple. It does not
change axis's behavior unless a user explicitely sets the new
configuration
option to "false". All in all, it's a very safe patch that provides big
bang
for the buck on the interop side of things.
Dave
_________________________________________
Dave Marquard ([EMAIL PROTECTED])
