axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James M Snell <jasn...@us.ibm.com>
Subject RE: Request that zero length array interop patch be applied in ti me f or 1.1 final
Date Thu, 20 Feb 2003 16:20:58 GMT
Hmm.. ok, I was reluctant to do this anyway ... and since it's been fixed 
in .NET 1.1, then I retract my original "this sounds reasonable" and give 
it a -1.

- James Snell
     IBM Emerging Technologies
     jasnell@us.ibm.com
     (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



ajbanck@informatica.com
02/20/2003 07:29 AM
Please respond to axis-dev


To
axis-dev@ws.apache.org
cc

bcc

Subject
RE: Request that zero length array interop patch be applied in ti       me 
f or 1.1 final



I would be in favour of this.
Note that this is fixed in .NET 1.1, when this patch is applied I would
propose to add a note to bugzilla for removal from the next Axis release
after .NET 1.1 is out. This to avoid accumulating bloat.

Thanks,

- ArentJan

-----Original Message-----
From: David Marquard [mailto:David_Marquard@forgent.com]
Sent: woensdag 19 februari 2003 23:46
To: 'axis-dev@ws.apache.org'
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 (dave_marquard@forgent.com)


Mime
View raw message