logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Smith <psm...@aconex.com>
Subject Re: [COMPATIBILITY] DOMConfigurator
Date Tue, 03 Jan 2006 02:07:22 GMT
I'd be ok with this being one of the binary compatibility breakages.   
I don't believe there would be too many people that had extended from  
DOMConfigurator.

Paul
On 03/01/2006, at 1:00 PM, Mark Womack wrote:

> I was looking at this class in regards to compatibility with 1.2.   
> I was interested in restoring the configureAndWatch methods.  This  
> should be easy to do and just have them use the new Plugin code to  
> provide the same functionality, but better because now the watchers  
> can be shutdown properly or stopped and replaced if the methods are  
> called multiple times.
>
> But there are host of other methods that have been removed since  
> DOMConfigurator now extends and uses JoranConfigurator for its  
> implementation.  Most of the removed methods were protected, so  
> their removal should only affect classes that subclass  
> DOMConfigurator.
>
> So, this is one of those questions of how far do we want to do in  
> restoring binary/source compatibility.  If we use  
> JoranConfigurator, then I think most of the protected methods make  
> absolutely no sense, but users that have extended DOMConfigurator  
> will need to rework their code.
>
> -Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>


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


Mime
View raw message