Please consider adding a LogLog.getQuietMode() method, so that I can save
the state of that variable and restore it later.
I'd like to use it in the new class below. Thanks!
Scott
/** A log4j SocketAppender that does not output a lengthy stack
* trace to the console when it can't connect. Intended to be
* used during development when Chainsaw may or may not be
* running.
*
* @author Scott Schram
*
*/
public class QuietSocketAppender extends org.apache.log4j.net.SocketAppender {
/** Creates a new instance of QuietSocketAppender */
public QuietSocketAppender() {
}
/** Called when all of the options are set.
*
* The LogLog quiet mode is turned on, connection attempted, then
* quiet mode turned back off.
*/
public void activateOptions() {
// @todo save and restore the current state of quiet mode when
they make the method public.
LogLog.setQuietMode(true);
super.activateOptions();
LogLog.setQuietMode(false);
}
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- What to do about commons-logging (if anything) Shapira, Yoav
- Re: What to do about commons-logging (if anything) Ceki Gülcü
- Re: What to do about commons-logging (if anything) Jacob Kjome
- RE: What to do about commons-logging (if anything) Shapira, Yoav
- RE: What to do about commons-logging (if anything) Scott Schram
- RE: What to do about commons-logging (if anything) Mark Womack
- RE: What to do about commons-logging (if anything) Lutz Michael
- RE: What to do about commons-logging (if anything) Mark Womack
- RE: What to do about commons-logging (if anything) David Janovy
- RE: What to do about commons-logging (if anything) Mark Womack
- RE: What to do about commons-logging (if anything) David Janovy