Certainly putting commons-logging and log4j in the container's
common/lib directory is the documented configuration. However this does
not allow application-level logging for libraries used by the
application like digester or spring that themselves use commons logging.
The application log messages they generate then end up in the
container's log files, and have to be enabled by changing the
container's logging config. This is far from ideal. Hence my desire to
install commons-logging in the application's WEB-INF/lib directory ..
when you hit the problem I encountered.
John.
Gregor Schneider wrote:
On Fri, Jan 30, 2009 at 8:33 PM, Rusty Wright <rusty.wri...@gmail.com> wrote:
Does that work reliably now? I was under the impression that it caused
problems, but that may have been with a previous version of tomcat. That's
why I asked my "where else" question; I was wondering if that's what he was
thinking of.
Since you're talking about TC 5.5, it's a definit yes.
Take a look at http://tomcat.apache.org/tomcat-5.5-doc/logging.html
I've got one 5.5-instance-running here, and it works like charm.
Rgds
Gregor
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
