RE: <isset> oddity

 



-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@...]
Sent: Wednesday, June 17, 2009 9:49 AM
To: user@...
Subject: Re: <isset> oddity

/*
On 2009-06-16, Rebhan, Gilbert <Gilbert.Rebhan@...> wrote:

> Conclusion = there seems to be a difference related to the handling
> of txt- and xmlproperties on different platforms, maybe it's caused
> by jdk/jre ?

Looked like a Java5/Java6 difference, maybe inside the XML parser.

> Should i open a bugreport ?

Yes, please do (so I can "untick" yur emails ;-)
*/

Bugreport opened, Patch attached =
https://issues.apache.org/bugzilla/show_bug.cgi?id=47381

It wasn't an issue with jdk, but the processNode Method in XmlProperty =

if (nodeText.trim().length() != 0 || emptyNode) {
                addProperty(prefix, nodeText, id);
            }

when trim removes all white spaces, so it works with =

if (nodeText.trim().length() >= 0 || emptyNode) {
                addProperty(prefix, nodeText, id);
            }

Works with ant 1.7.1, jdk 1.5.0_11 and jdk 1.6.0_07 on Windows 2000
Have to recheck on my machine later ..



Regards, Gilbert

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@...
For additional commands, e-mail: user-help@...