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 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From [EMAIL PROTECTED] 2005-01-03 15:31 ------- Some more information about xml:base attributes can be found e.g. here: http://xml.apache.org/xerces2-j/faq-xinclude.html or here: www.w3.org/TR/xmlbase/ They are obviously important parts of specifications like XLink or XInclude, which indicates that they indeed should be treated as normal attributes and kept in the set of configuration properties. As another workaround to your problem: Would it be possible to avoid the direct include in your XML document and instead use a ConfigurationFactory that reads the two XML documents from its definition file? If you place these files inside an <additional> section, a HierarchicalConfiguration will be constructed with the union of both documents. If this doesn't help, there is an enhancement request to provide a filter decorator (Issue 31281). This should be a solution because it would allow to transparently filter out the undesired attributes. Anyway, I am marking this bug as Wontfix because there is nothing we can do about these attributes directly. -- 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]
