[prev in list] [next in list] [prev in thread] [next in thread] 

List:       log4j-user
Subject:    RE: In Log4J 1.3alpha-6 DOMConfigurator.configureAndWatch() method has
From:       Mark Womack <womack () adobe ! com>
Date:       2005-07-27 16:08:09
Message-ID: 0IKA00FL2NHLJW () mailsj-v1 ! corp ! adobe ! com
[Download RAW message or body]

+1.  I think this falls into the "making sure 1.3 is as api compatible with
1.2 as we can make it" category.  Curt and Jake have done some good things
around this, but we should all review the areas we are familiar with.

In this particular case, we an probably even change the underlying
functionality to use the new FileWatchdog so that it will not create a new
thread every time it is called, and it will end the thread appropriately
when the repository resets/shutsdown.  But still deprecate it.

-Mark

> -----Original Message-----
> From: Scott Deboy [mailto:sdeboy@comotivsystems.com]
> Sent: Wednesday, July 27, 2005 9:02 AM
> To: Log4J Users List; womack@adobe.com
> Subject: RE: In Log4J 1.3alpha-6 DOMConfigurator.configureAndWatch()
> method has been removed
> 
> This is an api used by external folks (including myself) and we should
> deprecate the method instead of removing it.  If we need to put big
> warnings in the JavaDoc about usage and change the underlying
> implementation to use the new plugin framework, that's fine.
> 
> Scott


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

[prev in list] [next in list] [prev in thread] [next in thread]