Mailing-List: contact log4j-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@jakarta.apache.org>
Message-ID: <000901c1b4b6$3ae63ee0$d0673240@nuserve>
From: "Dan Lipofsky" <danlip@nuserve.com>
To: "Log4J Users List" <log4j-user@jakarta.apache.org>
References: <3C6A80C4.1010803@camline.com>
 <001101c1b4b0$419349a0$d0673240@nuserve>
 <02c301c1b4b0$dae97020$8b00000a@TariqM>
Subject: Re: double logs
Date: Wed, 13 Feb 2002 09:45:30 -0800
Organization: NuServe
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I don't mind the personal opinion expressed, but I would like to
know what is bad about my design and how to fix it.  I never
thought it was a great solution, but it was the only one I found.
Categories are named after the class they are used in, and appenders
were added to root until this problem came up, and now I add them
to my highest non-root level.  I thought this was textbook.
- Dan

T Master <tmaster@iknowledge.com> wrote:
> That just shows bad design in your Category/Logger design IMHO.
> Disclaimer: Personal opinion expressed. :D

Dan Lipofsky <danlip@nuserve.com> wrote:
> > I had a similar problem with log4j and tomcat.  See
> > http://www.mail-archive.com/log4j-user@jakarta.apache.org/msg03734.html
> > and the followups and see if it helps.  The key was turning off
additivity.
> > - Dan


--
To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>