Thanks.. Yeah, I was too thinking of putting at some central place.
-Original Message-
From: Wyss Patrick [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 07, 2007 9:17 PM
To: Log4J Users List
Subject: AW: Logging Strategy: Using multiple Loggers in same Class file
>
> > 2 Logger.getLogger in my class files. It solves my purpose but just
> > wondering if my approach is fine?
>
>
> It's perfect :-)
>
i'd put either the String "JobStatus" or the whole logger somewhere central
like into a singleton (to make sure you can change the loggers name easily) but
th
On 6/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
In my application, I wanted to use logging this way:
1. Use general log4j logging statement which goes to a project log file
(It works fine). For e.g logger.getLogger( "ToolCli.class" );
2. A special log which needs to be written t
Wouldn't that application be the sort of thing to use 'nested
diagnostic context' on?
NDC.push("filterable trans start message");
and pop the context in the 'finally' after the commit or rollback.
On 6/7/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Hi,
In my application, I wanted to use
Hi,
In my application, I wanted to use logging this way:
1. Use general log4j logging statement which goes to a project log file
(It works fine). For e.g logger.getLogger( "ToolCli.class" );
2. A special log which needs to be written to a separate file. Here we
are not concerned about the log
