commons-logging resides in tomcat/bin and dynamicaly binds to log4j / sdk logging.
this can cause some headaches, and apparently also some memory leaks, when you set up logging in your own web-app and wan't the two to work together. There is a nice wrapper called SLF4j which statically the commons api and log4j / sdk logging / others. Has anyone successfully replaced commons-logging in Tomcat with SLF4j ? Henrik --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
