Hi Martin, > I'm not sure I understand why you need this plugin (apart from the > reloading aspect). If you have log4j.jar in WEB-INF/lib and > log4j.properties in WEB-INF/classes, it should just work.
1.) First "the user is totally responsible for the configuration of the underlying logging system", so you have to load a log4j configuration file somewhere inside your application or use the log4j.configuration on startup . That might be not as flexible if you are deploying on several app-servers and habe no access to the app-server startup scripts ... 2.) The PlugIn reloads the log4j configuration file on change which is quite useful if you want to trace problems. 3.) Although http://jakarta.apache.org/commons/logging/api/org/apache/commons/logging/pac kage-summary.html states that the algorithm first searches for log4j then uses jdk 1.4 logging and otherwise uses default implementation, some of my coworkers had no luck, even with setting the org.apache.commons.logging.Log property on startup inside Resin. So we decided to use this short PlugIn. Bye Thomas
