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, by
> the way.
>
Yes, that's a bit weird. And for the application developer it's mostly
not that much important to know how Tapestry transforms classes. But the
debug messages in the developers's application package are important.
Anyway, for me it worked using a log4j filter, as described in an
earlier conversation on this list, see
http://www.nabble.com/T5%3A-How-to-configure-T5-not-to-display-unwanted-log-td16024408.html
It works. Thanks.
I don't think it makes a difference if you use logger or category in
your log4j.xml. Actually, I think category has been renamed to logger
at some point, so you might actually want to stick with logger.
You are right, I tried it.
Hth,
Lutz
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
