logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <Yoav.Shap...@mpi.com>
Subject RE: "Best practices" for definining log4j categories?
Date Fri, 02 Aug 2002 12:57:21 GMT
I never want to define our own design / use as a "best practice", as
that's for others to determine.

That said, we've used log4j in many projects, from very small to very
large (tens of thousands of classes, multi-GB JVMs, hundreds of
concurrent users).  We've always stuck with the very basic 
Logger logger = Logger.getLogger(MyClass.class.getName())

Approach as outlined in the manual.  We've always been very happy with
it.  It's easy to configure logging the way we want.  It's also easy to
turn logging up and down for the relevant parts of each app at runtime.
It's simple and it works, which is good enough for us ;)

Yoav Shapira
Millennium ChemInformatics

>-----Original Message-----
>From: Mschilli1@aol.com [mailto:Mschilli1@aol.com]
>Sent: Thursday, August 01, 2002 8:22 PM
>To: log4j-user@jakarta.apache.org
>Cc: log4perl-devel@lists.sourceforge.net
>Subject: "Best practices" for definining log4j categories?
>Hi there,
>we in the log4perl team (log4perl.sourceforge.net, a Perl port of
>wondering if there's any "best practices" for defining log4j
>Sure, from what I've read so far, categories are usually resembling the
>hierarchy of the software the logging code is used by.
>But are there any other recommendations or experiences shared by people
>having used log4j in huge projects?
>Would be great if you could provide pointers or share your own
>-- Mike
>Mike Schilli

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

View raw message