Martin wrote:
Found this helpful
http://tomcat.apache.org/tomcat-5.5-doc/logging.html
default logging is commons-logging with known limitation to Engines and
Hosts
this limitation of JDK Logging appears to be the genesis of per-web
application logging as the configuration is per-VM
That sounds great for Tomcat 5.
From what I understand Tomcat 6 logging has been overhauled and the
java.util.logging implementation was replaced with JULI, which understands how
to load per web app configuration files and make the corresponding
configuration available via the LogManager to the web app.
to overcome these limitations as well as the ability to configure in
Appenders (socket/file etc) replace with Log4j
http://logging.apache.org/log4j/1.2/index.html
I think Appenders are the same as Handlers in java.util.logging. So for those
going with Tomcat 6, JULI provides pretty much the same capabilities AFAIK
(Socket communication / Handlers / XML Format, etc.).
Ole
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
