cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: Log levels -> DEBUG?
Date Mon, 10 Mar 2003 15:48:29 GMT
On Mon, Mar 10, 2003 at 08:52:11AM -0500, Berin Loritsch wrote:
> Jeff Turner wrote:
> >> From src/webapp/WEB-INF/logkit.xconf:
> >
> >
> > ----------------------------
> > revision 1.13
> > date: 2003/02/12 10:58:59;  author: stefano;  state: Exp;  lines: +14 -14
> > lower the log level to ERROR (which gives better out-of-the-box
> > performance and better visibility of errors)
> >
> > That's all very well, but with Cocoon as broken as it is at the moment,
> > having logs is rather useful in getting rid of the errors :)
> >
> > Any opinions on ERROR, DEBUG or something in between?
> How about this:
> Focus your logs on what is important.  THe .xlog provides you with the
> ability to have fine-tuned control over the logging infrastructure.
> Route categories for which you really need to do your debugging.

Yes, makes sense.  The question is, do we start fine-tuning from DEBUG or
from ERROR?  Do we assume buggy-ness or correctness as the default? :)

> The Avalon team is getting ready to release a new version of the
> Excalibur Logger package, and I am getting ready to do a new build
> of it today as another release candidate.
> If you provide enough demand, I can add support to merge in the
> contents of a debug.xlog file (same directory as the first config
> file) to take care of adding those additional log targets to your
> log files.  From the debug.xlog file you would only be able to add
> additional categories and reference what is in the original
> configuration file--but it would be something you could use.

I'll let others speak here, as I'm one of those lazy people who hardly
understands the current syntax due to not having read the docs ;P


View raw message