Works great now, Scott. Thanks.
Take care,
--Lance
-Original Message-
From: Scott Deboy [mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 4:13 PM
To: Log4J Users List
Subject: RE: Trouble with chainsaw source code and build today
Sorry Lance,
Just committed.. Let me know if th
Sorry Lance,
Just committed.. Let me know if this didn't fix it.
Scott
-Original Message-
From: Lance Birtcil [mailto:[EMAIL PROTECTED]
Sent: Friday, January 16, 2004 4:00 PM
To: '[EMAIL PROTECTED]'
Subject: FW: Trouble with chainsaw source code and build today
Sorry to cross-post -
Sorry to cross-post -- I sent this to the log4j-dev list yesterday.
Has anyone here run into this problem?
--Lance
-Original Message-
From: Lance Birtcil [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 15, 2004 3:56 PM
To: '[EMAIL PROTECTED]'
Subject: Trouble with chainsaw source code
Just name your loggers with a dot notation, and they will be organized
into hieararchies. Each point will then be a 'placeholder' entry in
tree, unless you configure a logger with that name. One recommended
usage is to log to fully-qualified-classnames. Here's an pseudocode
example:
Myclass.doS
Howdy,
Read the short manual on the log4j site.
Yoav Shapira
Millennium ChemInformatics
>-Original Message-
>From: Joe Collins [mailto:[EMAIL PROTECTED]
>Sent: Friday, January 16, 2004 1:12 PM
>To: [EMAIL PROTECTED]
>Subject: creating a logging hierarchy
>
>Hi!
>
>Where do I create the
Hi!
Where do I create the hierarchy in log4j i.e. must I have a hierarchy of
class files or can I simply create loggers in the config.xml and if so
how do I create this hierarchy within the config.xml (i.e. syntax for
detailing logger x is a parent of logger Y). If loggers are created in
the con
Well if you do the second part:
private static final boolean DEBUG_ENABLED = LOG.isDebugEnabled();
then if you want to change your logging set-up you need to re-start the vm.
Not great in an app-server or web-server environment.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL P
There is no problem with using final with the logger as I see no reason
why you would want to obtain
another logger instance post class initialization.
However, using a final boolean for the DEBUG flag would prevent the class
from detecting any run time
changes to the classes's level during th
Howdy,
>private static final Logger LOG = Logger.getLogger(MyClass.class);
This is good and I do it as well as recommend it to others.
>private static final boolean DEBUG_ENABLED = LOG.isDebugEnabled();
This is not good because isDebugEnabled potentially changes with time
during a program's ex
I always spot my mistakes that moment after hitting send - of course it should be -
private static final Logger LOG = Logger.getLogger(MyClass.class);
private static final boolean DEBUG_ENABLED = LOG.isDebugEnabled();
>
> From: <[EMAIL PROTECTED]>
> Date: 2004/01/16 Fri PM 05:30:29 GMT
> To: [EM
While with my mind on some unrelated performance issues in a project I scanned through
some tips in http://www.javaperformancetuning.com
The ones in http://www.javaperformancetuning.com/tips/final.shtml made me think that
maybe the best logger definition whould be -
private static final LOG = L
>> I would log to the database. In the same transaction as the operation you
want to log about. <<
Beware ... this approach will never record any failed transactions, because the
logging will be rolled back along with everything else!
It really depends on what you really mean by 'reliability'. I
12 matches
Mail list logo
