Lutz Hühnken schrieb:
Hm... I had the same problem once, and I figured it was because
Tapestry doesn't use the log level configured for the
"org.apache.tapestry5" category, but the level you define for your
components.
> ...
> That is something I find quite annoying and don't see much use in,
Hm... I had the same problem once, and I figured it was because
Tapestry doesn't use the log level configured for the
"org.apache.tapestry5" category, but the level you define for your
components.
As it is said on http://tapestry.apache.org/tapestry5/guide/logging.html :
When a component's logger
Ah, okay.
No, you don't have to configure SLF4J - it's using log4j by default.
Looks like Sven might have given the answer you need. Does it work if
you use instead of ?
-Filip
Andy Pahne skrev:
No, that's not the case if you use log4j XML configuration file format.
Still no idea...
Do
2008/8/11 Andy Pahne <[EMAIL PROTECTED]>
>
> I tried to setup Tapestry5 logging to level "info", but all "debug"
> messages are still logged. I think I did what the documentation told me to
> do
>
No, that's not the case if you use log4j XML configuration file format.
Still no idea...
Do I have to configure SLF4J or is it sufficient to configure log4j?
Andy
Filip S. Adamsen schrieb:
Hi,
You need to prefix the logger name with log4j.category. or it won't work.
Or, at least that's h
Hi,
You need to prefix the logger name with log4j.category. or it won't work.
Or, at least that's how it was back when I used log4j - I'm now using
SLF4J with Logback and I'm not going back. :)
-Filip
Andy Pahne skrev:
I tried to setup Tapestry5 logging to level "info", but all "debug"
me
I tried to setup Tapestry5 logging to level "info", but all "debug"
messages are still logged. I think I did what the documentation told me
to do
http://tapestry.apache.org/tapestry5/guide/logging.html
Can anybody tell me what I am missing?
from my log4j.xml:
