RFR: 8043306 - Provide a replacement for the API that allowed to listen for LogManager configuration changes

Alan Bateman Alan.Bateman at oracle.com
Fri Sep 12 12:37:23 UTC 2014

On 12/09/2014 11:45, Daniel Fuchs wrote:
> I am still unconvinced this is worth the additional
> complexity it would bring to the implementation.
> The deprecated methods were using HashMap to store listeners,
> and therefore the order in which listeners were invoked was also
> undefined. Nobody has ever complained.
I'm not convinced either. The previous methods were rarely used (prior 
to their deprecation and eventual removal there was a static analysis 
done on tens of thousands of projects to get some data on actual usage 
and there were only a handful of actual usages). The only reason for 
introducing alternative methods is that there is a solution for the tiny 
number of cases where LogManager can't be sub-classes. So I think it's 
best to keep it as simpler as possible.


More information about the core-libs-dev mailing list