This is such a stupid bug that its lame to be compatible with it.
I of course understand the "bang for the buck" argument, but it
feels so unethical and so dirty.

Boy, I thought Web services was spsed to allow us to get away
from having to be "bug compatible" with crappy software. Oh well.

Sanjiva.

----- Original Message -----
From: "James M Snell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 20, 2003 4:50 AM
Subject: Re: Request that zero length array interop patch be applied in time
f or 1.1 final


> 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])

Reply via email to