Oops; more stumbling. I think it's usually Commons Logging that causes
problems with tomcat, and perhaps elsewhere, not log4j. slf4j is a Commons
Logging alternative.
Rusty Wright wrote:
What I just wrote is probably confusing; I'm using slf4j with logback
for logging, not log4j. You don't
What I just wrote is probably confusing; I'm using slf4j with logback for
logging, not log4j. You don't need a logback.xml configuration file if you're
using slf4j with log4j (but you will need a log4j configuration file).
I prefer logback because with tomcat you can never be sure that any pro
I also vote for slf4j. If you need a "for example", here's my logback.xml
file, which lives in the WEB-INF/classes directory:
%5level: [%thread] %class.%method.%line:
%message%n
I use slf4j!
use slf4j-log4j when development!
use slf4j-jdk log when GAE Server!(change slf4j-log4j to slf4j-jdk-log
before GAE appcfg update war)
2010/2/2 Alex
> Hello,
>
> Has anyone tried to use Log4j in production GAE? Is it supported?
>
> According to Java GAE docs, only java.util.logging
Hello,
Has anyone tried to use Log4j in production GAE? Is it supported?
According to Java GAE docs, only java.util.logging is fully supported.
See http://code.google.com/appengine/docs/java/runtime.html#Logging
[...]
Any logging framework (such as log4j) that logs to the output or
error stream
