Re: Bug report comments requested

Hey Ulrich,

it seems the solution to this problem is quite simple after all. Could 
you verify this works for you?

cheers,

- Leo

-------- Original Message --------
Subject: Re: Bug report comments requested
Date: Fri, 10 Jan 2003 09:43:00 -0500
From: Peter Royal <[email protected]>
To: Leo Simons <[email protected]>

On Friday, January 10, 2003, at 07:54  AM, Leo Simons wrote:
> Ulrich Mayring wrote:
>> Hello,
>> could someone please comment on Phoenix bug #15846
>
> this behaviour looks to be deliberately introduced in may last year:
>
> http://cvs.apache.org/viewcvs.cgi/jakarta-avalon/src/java/org/apache/ 
> avalon/framework/configuration/SAXConfigurationHandler.java
>
> (look at rev1.20). It's got nothing to do with phoenix I think; it's  
> in avalon-framework. I'm contacting the developer who made the change  
> (Hi Peter!) directly to ask for feedback
>
> Changing the behaviour back might lead to breakages in other areas.  
> I'm not sure what to do at this point. Anyone else have a suggestion?

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.

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").
-pete