JMX is an important feature for me as well in Log4j. One thing that may be simple to implement is JMX MBeans that directly update the Log4j configuration files, and then issues a reload request to Log4j.
Log4j already supports doing reloads of it's config during runtime, and by having the JMX MBeans update the config files the changes are persisted across app restarts. What do you think? Later Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
