On Tue, 7 Aug 2001 15:12, giacomo wrote:
> > Peter, what do you think of adding two additional log levels
> > below DEBUG in LogKit?
> >
> > The new hierarchy of debug levels would be:
> >
> > INFRASTRUCTURE
> > CLASSLOADER
> > DEBUG
> > INFO
> > WARN
> > ERROR
> > FATAL_ERROR
> >
> > Alternatively, we could call them DEBUG3 and DEBUG2 respectively,
> > but it does not capture the intent of those log levels properly.
>
> And I lately had the need for a log level between DEBUG and INFO which
> I'd like to call TRACE. This was because we used (esp. Cocoon) the DEBUG
> level for exactly that but had the need to separate out other (tracing)
> information that doesn't belong to the INFO level. In the environment
> our Avalon/Cocoon application is running the levels INFO and higher will
> be used by the support staff to detect failures and anomalies.
I used to have another level in there - EDEBUG for Extreme DEBUGing ;)
However I still think that what you probably want is more fine grain
categorys setup. That way each category (or channel, or subject or whatever
you call it) is explicitly setup to carry a certain type of information and
can control it more effectively. Could this work with Cocoon?
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
