Ulrich Mayring wrote:
this behaviour looks to be deliberately introduced in may last year:Hello,could someone please comment on Phoenix bug #15846
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?
A workaround would be (rather extensive) modification of phoenix to not use the SAXConfigurationHandler but your own version.
and Cornerstone bug #15844.definately sounds like a bug to me allright. Will happily apply a patch.
As to releases, I need to figure out how to do that before I can do so...and a release of fortress is higher on my agenda atm. It'll hence be a while if I do it.
My boss is pestering me why I don't upgrade Avalon/Phoenix/Cornerstone and I have to give him some kind of answer.I'd say there's a backwards compatibility problem and you're hoping to have it fixed @ avalon, and are waiting for that.
cheers,
- Leo
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
