Howdy,
In my webapp's context I configured a logger:
Logger className=org.apache.catalina.logger.FileLogger
prefix=localhost_gargantus_log.
suffix=.txt
timestamp=true /
I changed over from using log4j to using the native java.util.logging
package, and I have lost the ability to write to this logger in my
context. Instead, java.util.logging logs to the file I specify (or a
default) in its own configuration file.
How come log4j was able to direct logging to the tomcat logger above?
My guess: because log4j is better and has features specifically
tailored for servlet context logging?
Can anybody shed some light on this situation?
Light? No. Suggestion? Yes: reverse your switch and use log4j.
Yoav Shapira
This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged. This
e-mail is intended only for the individual(s) to whom it is addressed, and may not be
saved, copied, printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your computer system
and notify the sender. Thank you.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
