DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32799>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32799 ------- Additional Comments From [EMAIL PROTECTED] 2004-12-23 18:21 ------- Hi Oliver, thanks for your information. Yes, I can confirm that the example uses Xalan 2.6.0 with the xerxes parser. I also have little knowledge of parsing XML, so I cannot help a lot. I understand that from a configurations point of view, the new behaviour of HierarchicalXMLConfiguration is correct in the nightly builds now. Nevertheless, it differs from the current release 1.0, which does not contain those xml:base-Keys in the result of getKeys(). As the new behaviour of HierarchicalXMLConfiguration is to be considered correct and will be included in the next release, I just do the following in my code now: Read in the XML-file, iterate over all keys and insert all keys but the xml:base-keys in a new object of typ HierarchicalXMLConfiguration. That works fine for me and serves as a good workaround. Perhaps, as a future enhancement, HierarchicalXMLConfiguration could contain a removeKeys(Iterator keysToBeRemoved)-method that can be used to remove those unwanted keys directly from the configuration. A call could be like this: myConfig.removeKeys(myConfig.getKeys("[EMAIL PROTECTED]:base]")); But for the moment, I have a usefull workaround, so I probably just don't care about this during the next weeks. Best regards, Christian Kemmer -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
