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=36384>. 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=36384 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From [EMAIL PROTECTED] 2007-01-28 21:00 ------- I'm going to reopen this one. Basically the deficiency is that every other included appender with the exception of the org.apache.log4j.rolling.RollingFileAppender can be configured by either the PropertyConfigurator or the DOMConfigurator while the new RFA can only be configured by the DOMConfigurator. If you have an existing property file configuration and decide to extend it to include a o.a.l.r.RFA, then you would have rewrite the whole configuration as an XML configuration file. This is similar to https://issues.apache.org/jira/browse/LOGCXX-102 which includes a patch to log4cxx to support configuration of o.a.l.r.RFA through the property configurator. While I have some issues with putting RFA specific code in PropertyConfigurator (as the patch does), it does show that it is not technically insurmountable to modify property configurator to support the new RFA. My preferred process would be to come up with a fix in log4j and then port the fix over to log4cxx. -- 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]
