>> 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.
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.
