avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Donald <dona...@apache.org>
Subject Re: [excalibur]Hierarchy management in LogKitManager
Date Tue, 11 Sep 2001 07:25:26 GMT
On Tue, 11 Sep 2001 17:19, Sylvain Wallez wrote:
> Hi folks,
> Looking at the recent change in LogKitManager, I was wondering about the
> Hierarchy management. At first, the LogKitManager used the default
> hierarchy, and now it always creates a new one.
> While this doesn't affect components that get their logger through the
> ComponentManager, it does affect logging of low-level non-component
> classes that get a logger using Hierarchy.getDefaultHierarchy(). I have
> plenty of them here (switched to LogKit from Log4J in which this is the
> preferred way).
> So, it would be good for the Hierarchy management to be configurable in
> LogKitManager :
> - at the minimum with a boolean configuration telling whether using the
> default hierarchy or creating a new one.
> - at the best with a pluggable HierarchyFactory.

or how about something as simple logKitManager.setHierarchy() ? If not set it 
could default to a new hierarchy ?



We should take care not to make the intellect our 
god; it has, of course, powerful muscles, but no 

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

View raw message