RE: Help understanding Log4j basics

2010-11-25 Thread Bender Heri
> I've previously searched the manual and I understand the hierarchy of: > DEBUG < INFO < WARN < ERROR < FATAL > However, I'm interested in in learning if there is a way to print ONLY > one level rather than the target level and all levels above it. Unless > I've missed it, the manual does not expl

Re: Help understanding Log4j basics

2010-11-23 Thread Ari King
>> 2. How does one stop log4j in a webapp? > > Configure it via log4j config, then restart webapp (this reloads > configuration) After reviewing the manual, as I understand it the way to turn "off" logging is by not assigning a log level or assigning a high (error or fatal) log level. But doesn't

Re: Help understanding Log4j basics

2010-11-23 Thread Christian Grobmeier
> 1. How does one start log4j in a webapp? Is having the > log4j.properties or log4j.xml file in the classpath enough? Usually yes. You should have log4j itself in the classpath, of course. > 2. How does one stop log4j in a webapp? Configure it via log4j config, then restart webapp (this reloads

Help understanding Log4j basics

2010-11-23 Thread Ari King
I'd appreciate help in clarifying the following: 1. How does one start log4j in a webapp? Is having the log4j.properties or log4j.xml file in the classpath enough? 2. How does one stop log4j in a webapp? 3. Is there a way to specify which level of logging, i.e. debug, info, error, is printed? Tha