Tapestry 3.1 and logging

[Henri Dupre <he...@gmail.com>]

Just read in the Jboss forums about issues with commons logging and
there are details about memory leaks with it:
http://www.szegedi.org/articles/memleak.html
Maybe this library is causing all the redeployement issues in tomcat.

I think it would be nice to go back to log4j (only) with Tapestry 3.1
and eventually restore the logging panel in the inspector... That was
a nice idea. I'm not sure how many people are using the jdk logging
and really need commons-logging.

Henri.

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org