avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: [excalibur]Hierarchy management in LogKitManager
Date Tue, 11 Sep 2001 11:55:41 GMT
Peter Donald wrote:
> On Tue, 11 Sep 2001 18:13, Sylvain Wallez wrote:
>>Peter Donald wrote:
>>>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 ?
>>Sure, it's way simpler ;)
>>And even simpler : two constructors, one with no parameters (new
>>hierarchy) and one with an existing Hierarchy. Patch attached !
> Works for me. Applied.

BTW, I didn't noticed, but the Reply-To header points to your address 
instead of the list.

Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com

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

View raw message