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=43619>. 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=43619 ------- Additional Comments From [EMAIL PROTECTED] 2007-10-23 13:00 ------- The attached file only adds the pluggable property resolver to the PropertyConfigurator. It does not appear to affect the DOMConfigurator. I'd be relunctant to add a new capability to PropertyConfigurator without a consistent equivalent for DOMConfigurator. You may be able to address your use case with a couple of different approaches that would not require modifications to log4j. Since older log4j's are widely deployed and hard to displace, it would probably be in your interest to use capabilities in those versions when at all possible. If you would be willing to extend DOMConfigurator, you could override DOMConfigurator.subst(String) and accomplish the same type of goal by passing in a specialized implementation of Properties downstream. You could also extend PropertyConfigurator.configure(Properties, LoggerRepository) and wrap the passed Properties object with a specialized implementation of Properties that will also pull properties from JMX. System properties would still be checked in preference to properties defined in the config file or in JMX, but that might be sufficient for your needs. -- 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]
