At 09:37 PM 11/28/2004, Mark Womack wrote:
OK. Then we should change the name of the event to firePluginAdded instead of firePluginStarted, and we should find a different way to report that a plugin has been started, if it is important.
No because I doubt anyone would be interested in the fact that the plugin was added to the PR. The firePluginStarted method should be called after the activating the plugin and adding it to PR. However, firePluginStarted could be renamed to firePluginActivated.
Mark, keep in mind that the current impossibility for us to stop the watchdog thread at LoggingRepository shutdown, constitutes a very serious bug. We MUST be able to cleanly stop the watchdog thread at LoggingRepository shutdown, otherwise application servers like Tomcat cannot cleanly recycle the application. (I cannot over emphasize the importance of this problem.)
Yeah, it is serious. Using the plugin architecture for watchdogs will solve this issue since plugins are shutdown properly when the repository is shutdown.
Real test cases proving this would be nice. I just realized that DBReceiver would not be closed on LogManager.shutdown. (Another case of acute do-as-i-say-not-as-i-doitis.)
Darn reformat/reinstall. How's this message?
Just perfect. :-)
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/eclm
Professional log4j support: http://qos.ch/log4jSupport
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
