Vadim Gritsenko wrote:
>
> > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
> >
> > 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?
>
Yes, they are - if you don't specify own configurations, so a line
like <category name="startup" log-level="DEBUG"/> configures this
subcategory to have absolutely no target. In my eyes are the
three lines for the sub-categories not necessary as they should
get the same configuration.
I saw your patch for this and this is fine as well for me, also
a the following lines achieve the same:
<category name="core" log-level="DEBUG">
<log-target id-ref="core"/>
<log-target id-ref="error"/>
</category>
Thanks,
Carsten
Open Source Group sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.s-und-n.de mailto: [EMAIL PROTECTED]
================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
