;t provide much of an improvement.
Thanks for taking time to look at this issue.
-Faheem
-Original Message-
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Friday, March 09, 2007 1:05 PM
To: Log4J Users List
Subject: Re: Using LogManager.getLogger(String)
On Mar 9, 2007, at 9:03 A
On Mar 9, 2007, at 9:03 AM, Zakaria, Faheem wrote:
I would like to clarify the first paragraph further.
Legacy Code: (cannot be modified)
...
OurLogger.log(new LogObject("com.myclass", level.DEBUG, "Log Message
1"));
OurLogger Class: (can be modified)
public static voi
ers List
Subject: RE: Using LogManager.getLogger(String)
Hey Curt,
Thank you for getting back to me.
Currently, legacy code uses a static method access logging
functionality. Furthermore, the methods signature accepts an Object
populated with class name, level, etc. We cannot modify the legac
nt: Friday, March 09, 2007 2:39 AM
To: Log4J Users List
Subject: Re: Using LogManager.getLogger(String)
On Mar 8, 2007, at 4:26 PM, Zakaria, Faheem wrote:
> Since this is a legacy system, our
> plan is to lookup the Log4j Logger on every log request through
> LogManager.getLogger(String).
On Mar 8, 2007, at 4:26 PM, Zakaria, Faheem wrote:
Since this is a legacy system, our
plan is to lookup the Log4j Logger on every log request through
LogManager.getLogger(String).
Could you explain your reasoning here. Maybe give some examples of
the existing logging calls in your code and
Hello,
I am working on refactoring an existing application with a proprietary
logging framework. We are integrating with Log4j and need to understand
performance/scalability as well as any best practices surrounding the
use of LogManager.getLogger(String). Since this is a legacy system, our
plan
