Re: When to log? (best practices and localization)
- From: apm35@xxxxxxxxxxxxxxxxxx
- Date: Fri, 31 Aug 2007 07:54:05 -0700
On 31 Aug, 14:51, Lew <l...@xxxxxxxxxxxxx> wrote:
I'm rather vague on what I really want to ask here, I simply don't
know when to use a logging tool and when System prints are "enough".
Always use a logging tool. System prints are never "enough"; they are always
too much. Always use a logging tool, Always.
I have set up my IDE templates for Java classes to include the import of the
logging library and declaration of a "logger" instance variable.
Sounds like very good advice IMO. I would recommend using log4j to do
the logging.
-Andrew Marlow
.
- References:
- When to log? (best practices and localization)
- From: Karsten Wutzke
- Re: When to log? (best practices and localization)
- From: apm35
- Re: When to log? (best practices and localization)
- From: Karsten Wutzke
- Re: When to log? (best practices and localization)
- From: Lew
- When to log? (best practices and localization)
- Prev by Date: Re: When to log? (best practices and localization)
- Next by Date: swing widgets: Who's got the focus?
- Previous by thread: Re: When to log? (best practices and localization)
- Next by thread: Re: When to log? (best practices and localization)
- Index(es):