For version 1.3, we are looking to deprecate the configureAndWatch() method and replace it with a more complete implementation, ConfigWatchdog. Tne implementation will not be tied to a specific configurator, but will support any configurator. There has been a review of the design on the dev mailing list, and I recommend those interested dig around in the archives (look for the "Watchdog Nickel Tour").
Providing a mechanism for watchdogs to be configured via a configuration file is on the list of features to be implemented once the base functionality is in place. -Mark -----Original Message----- From: Bomb Diggy To: [EMAIL PROTECTED] Sent: 6/12/02 1:08 PM Subject: Re: Re-read configuration file via configureAndWatch() There was a post a couple of months ago about being able to 'set' configureAndWatch() via the log4j.properties file. http://www.mail-archive.com/log4j-user@jakarta.apache.org/msg04352.html Is this feature planned for future releases of Log4J? I hacked on the source a little and managed to get it working. Totally cool, but my hack is just that. Log4J now automatically finds my log4j.properties file (in the Tomcat classpath) and tells itself to reload every 60 seconds. The code snippet is at: http://www.acromedia.com/PCUpdate.html __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
