Return Receipt
Your RE: An appender based on application level and on class
document hierarchy
:
Return Receipt
Your RE: An appender based on application level and on class
document hierarchy
:
ppender as
the caller.
Dominique
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: lundi 14 juin 2004 20:27
To: Log4J Users List
Subject: RE: An appender based on application level and on class hierarchy
Which logger variables are you referring to exactly?
At 08:19 PM
PROTECTED]
Sent: lundi 14 juin 2004 14:31
To: Log4J Users List
Subject: RE: An appender based on application level and on class hierarchy
Check out log4j 1.3 from CVS and follow the examples under
/examples/tiny-webapp/.
The most important point to remember is to declare the logger variables in
based on application level and on class hierarchy
Check out log4j 1.3 from CVS and follow the examples under
/examples/tiny-webapp/.
The most important point to remember is to declare the logger variables in
classes (in your toolkit) as instance variables and not as static class
variables
tried /examples/tiny-webapp/.
At 02:16 PM 6/14/2004, you wrote:
We have servlets, EJB, JSP...
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: lundi 14 juin 2004 14:14
To: Log4J Users List
Subject: Re: An appender based on application level and on class hierarchy
What type of
We have servlets, EJB, JSP...
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: lundi 14 juin 2004 14:14
To: Log4J Users List
Subject: Re: An appender based on application level and on class hierarchy
What type of applications are these?
At 02:06 PM 6/14/2004, you
What type of applications are these?
At 02:06 PM 6/14/2004, you wrote:
Hi,
I have multiple applications which are sharing different classes
(toolkit). I would like to know which is the best technique to have a
log file per application and if a log message is done in a shared class
the information
Hi,
I have multiple applications which are sharing different classes
(toolkit). I would like to know which is the best technique to have a
log file per application and if a log message is done in a shared class
the information will be sent to the application log and not to a 'class'
log. In fact
