avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ulrich Mayring <u...@denic.de>
Subject Re: Bug report comments requested
Date Fri, 10 Jan 2003 16:03:38 GMT
Leo Simons wrote:
 > Hey Ulrich,
 >
 > it seems the solution to this problem is quite simple after all. Could
 > you verify this works for you?

It does. But... (see below)

 > I was fixing a change that occured in v1.16. In 1.16 support was added
 > for putting xml:space=preserve as an attribute to control the
 > preservation of whitespace at the element level. With that change the
 > <tag/> syntax was returning empty string whereas previously it was
 > returning null.

In our version of Phoenix (pre 4.0) it was not returning null, but the
empty string.

As far as I see it, now it is not possible anymore to distinguish
between "empty element" (returns "") and "element not present" (returns
null). Many of our applications use these tests.

Or do you mean that putting xml:space="preserve" at the root element, we
will continue to be able to use these tests without any side-effects?

The key question is: can we get the v1.15 behavior back by putting
xml:space="preserve" at the root node?

 > My 1.20 change merely restored the behavior of returning null. If the
 > empty-string behavior is desired, one can put xml:space=preserve as an
 > attribute of the root element and it should flow down to all child
 > elements (it is inherited, so if you enable it at a higher level you
 > must explicitly disable it at a lower level with xml:space="anything
 > that isn't preserve").

Sorry if I sound confused, I'm just trying to determine, what the exact
consequences are for our applications :)

cheers,

Ulrich



--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message