cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: Logging/Reporting in the CLI
Date Sat, 27 Sep 2003 06:45:25 GMT
On Fri, Sep 26, 2003 at 08:48:51AM +0100, Upayavira wrote:
> I've been planning to extend the xml broken links file creation to 
> report a lot more, for example which uris were generated, which uris 
> were skipped, how big the pages were, etc, etc.
> I started wondering, which is more useful: to have the CLI create its 
> own report file, or to just use the standard Cocoon logging.
> Because, presumably, with the Avalon logging code, the user could (to 
> some extent at least) configure it to display information how they want. 
> For example, if I used different logging categories for each kind of 
> information, e.g. bean.generation.broken for broken links, 
> bean.generation.success for successfully created links.
> Which is better? A CLI specific report file, or Avalon logging?

IMHO, a CLI-specific report.  I see logging as orthogonal to
functionality provided.  I think it should be possible to safely turn off
all logging and not affect the output of Cocoon.  Tying the log system to
a piece of functionality seems like mixing concerns.


> If the latter, can someone tell me how to switch dynamically between 
> logging categories? (As you'll see from my code, I've never really 
> grappled with logging, and really don't know how to work with it yet).
> Regards, Upayavira

View raw message