cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vadim Gritsenko" <vadim.gritse...@verizon.net>
Subject RE: Strange Logging Behaviour
Date Fri, 26 Apr 2002 17:54:59 GMT
> From: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
> 
> I just found two strange things about logging in Cocoon:
> 
> a) If the logger category for a component is not configured in the
> cocoon.xconf
>    (via the logger attribute), it logs by default into "core.manager".
>    According to the configuration in web.xml, this should be just
"core".
> 
> b) The following lines in the cocoon.xconf make me a little bit
wonder:
> 
>     <category name="core" log-level="DEBUG">
>       <category name="startup" log-level="DEBUG"/>
>       <category name="roles" log-level="DEBUG"/>
>       <category name="manager" log-level="DEBUG"/>
> 
>    These lines achieve that anything logged to the category
core.manager (or
>    core.roles or core.startup) is ignored(!) and never logged.

Aren't log targets inherited by nested categories?

Vadim


>    And as core.manager is the default, all logging done by custom
components
>    (which have no logger attribute) will never make it's way into the
logs!
> 
> Or did I oversee something?
> 
> Bye
> 
> Carsten
> 
> Open Source Group                        sunShine - b:Integrated
> ================================================================
> Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
> www.s-und-n.de                      mailto: cziegeler@s-und-n.de
> ================================================================


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message