logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boddapati, Vijaya" <Vijaya.Boddap...@ibx.com>
Subject RE: PropertyConfigurator.configureAndWatch
Date Thu, 06 Oct 2005 13:13:37 GMT
 I have gone thru the latest log4j API and I have extended FileWatchDog
class and implemented doOnChange() method.

 My basic idea is to write a wrapper class that will consist of static
methods for debug, info, warn and error logging. And can call only these
methods directly for logging. Is there any way that I can access these
methods statically, and loading the properties dynamically. If I use
static block for loading the properties, then the properties can not be
loaded dynamically. But if I use constructor to load the properties, I
need to call the constructor at every time I log the message. And
another way is to create a non-static method and call it in all of the
static methods which is not optimal. Please suggest how to proceed on

Thanks in advance.


-----Original Message-----
From: Mark Womack [mailto:mwomack@apache.org] 
Sent: Wednesday, October 05, 2005 10:33 PM
To: Log4J Users List
Subject: Re: PropertyConfigurator.configureAndWatch

You are right.  We should not have removed the api, and reviewing the
changes we have made is a task for the 1.3 beta.  We should look at what
different and if we want to live with it, put it back, deprecated it,

I believe that, yes, configureAndWatch could be implemented with the 
FileWatchdog.  It will probably have slightly different behavior (like
allowing multiple watchers from multiple calls to the method), but I
it would be better behavior.  Or we could leave it.  The big deal
was that there was not way to shutdown the watcher in the web server 
environment.  This would be fixed with the new plugin stuff.


----- Original Message ----- 
From: "Scott Deboy" <sdeboy@comotivsystems.com>
To: "Log4J Users List" <log4j-user@logging.apache.org>
Cc: "Log4J Developers List" <log4j-dev@logging.apache.org>
Sent: Wednesday, October 05, 2005 8:36 AM
Subject: RE: PropertyConfigurator.configureAndWatch

We can't remove the api without deprecating it 1st, so log4j 1.3 should
support the configureandwatch methods.

Is the plan to have domconfigurator.configureandwatch (and
propertyconfigurator?) leverage a watchdog?  I thought we had discussed
this before but don't see it in the mailing list archive.


To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

CONFIDENTIALITY NOTICE: This E-Mail is intended only 
for the use of the individual or entity to which it is addressed and may contain information
that is privileged, confidential and exempt from disclosure under applicable law. If you have
received this communication in error, please do not distribute and delete the original message.
 Please notify the sender by E-Mail at the address shown. Thank you for your compliance.

To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org

View raw message