At 09:01 AM 8/2/2001 -0400, Berin Loritsch wrote:
>In developing with Cocoon, it has become clear that three
>levels of debugging may in fact be just what the doctor
>ordered. Let me give you a scenario:
>
>Excalibur's ComponentManager and ComponentSelector and
>friends output _alot_ of debugging code. It is what
>makes it so easy to maintain. However, I don't want
>to clutter the logfile with all that information unless
>I really need to. Therefore I need a base log level
>for INFRASTRUCTURE, so that I can see the inner workings
>if I wanted to.
As a fellow Cocoon2 user, I definitely see the itch you are trying to
scratch with this, but could it not be solved by using different log
categories? You could have a "classloader" category and a
"componentmanager" or more generic "avalon" category and just set the
priority to info if you don't care about their debug info. Of course what
might be needed is the ability for the ExcaliburComponentManager to be able
to give the components that it manages a different logger category from the
one that it uses itself. That is something that could be easily specified
in an .xconf somewhere (as a tag on the root element perhaps?)
Of course, this all ties in with the desire to be able to control LogKit's
configuration dynamically rather than programmatically. That was one cool
feature that Log4j had.
-pete
--
peter royal -> [EMAIL PROTECTED]
managing partners, inc. -> http://www.managingpartners.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
