You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Neeme Praks <ne...@apache.org> on 2008/09/17 18:01:33 UTC
[T5] DEBUG level logging in pages/components
Hi,
While debugging with Tapestry5, I noticed one not-so-nice issue. But
first, a bit of background.
I usually configure my logging framework (log4j) to log all statements
for my application at debug level during development. E.g. all log
records logged to "com.mycompany.myapp" logging category get printed at
DEBUG level. All other categories are usually at INFO level. This allows
me to focus on the log statements that I have written and ignore all the
verbose DEBUG logs of 3rd party libraries.
Back to Tapestry5. I have configured by log4j as usual (my stuff at
DEBUG level, everything else at INFO level). Although I expect to see
only the log output produced by MY CODE, I also see some debug output
produced by Tapestry internals. Seems that Tapestry class enhancement
code logs to the same log category as the class name being enhanced. And
the log statements are quite big (documenting the changes being made to
the original classes), resulting in lots of unwanted noise in my logs.
Example:
I have a page: com.mycompany.myapp.pages.MyPage
T5 class enhancement code logs its bytecode manipulation operations to
log category "com.mycompany.myapp.pages.MyPage", at DEBUG level.
This is not very nice, as I'm totally uninterested in seeing all this
verbose T5-internal logging.
I understand that it might be beneficial to have that class name as part
of the logging category (or maybe not), but at the very least, I would
recommend to add a T5 prefix to all those categories. The log category
in above example would then become something like
"org.apache.tapestry.classenhance.com.mycompany.myapp.pages.MyPage".
What do you think?
Something like this already planned? Or should I add it to JIRA?
Rgds,
Neeme
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [T5] DEBUG level logging in pages/components
Posted by Neeme Praks <ne...@apache.org>.
Added:
https://issues.apache.org/jira/browse/TAPESTRY-2684
Rgds,
Neeme
9902468 wrote:
> +1, I've encountered this annoyance too... I'd say add Jira issue.
>
> Neeme Praks wrote:
>> Hi,
>>
>> While debugging with Tapestry5, I noticed one not-so-nice issue. But
>> first, a bit of background.
>>
>> I usually configure my logging framework (log4j) to log all statements
>> for my application at debug level during development. E.g. all log
>> records logged to "com.mycompany.myapp" logging category get printed at
>> DEBUG level. All other categories are usually at INFO level. This allows
>> me to focus on the log statements that I have written and ignore all the
>> verbose DEBUG logs of 3rd party libraries.
>>
>> Back to Tapestry5. I have configured by log4j as usual (my stuff at
>> DEBUG level, everything else at INFO level). Although I expect to see
>> only the log output produced by MY CODE, I also see some debug output
>> produced by Tapestry internals. Seems that Tapestry class enhancement
>> code logs to the same log category as the class name being enhanced. And
>> the log statements are quite big (documenting the changes being made to
>> the original classes), resulting in lots of unwanted noise in my logs.
>>
>> Example:
>> I have a page: com.mycompany.myapp.pages.MyPage
>> T5 class enhancement code logs its bytecode manipulation operations to
>> log category "com.mycompany.myapp.pages.MyPage", at DEBUG level.
>>
>> This is not very nice, as I'm totally uninterested in seeing all this
>> verbose T5-internal logging.
>>
>> I understand that it might be beneficial to have that class name as part
>> of the logging category (or maybe not), but at the very least, I would
>> recommend to add a T5 prefix to all those categories. The log category
>> in above example would then become something like
>> "org.apache.tapestry.classenhance.com.mycompany.myapp.pages.MyPage".
>>
>> What do you think?
>> Something like this already planned? Or should I add it to JIRA?
>>
>> Rgds,
>> Neeme
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [T5] DEBUG level logging in pages/components
Posted by 9902468 <vi...@cerion.fi>.
+1, I've encountered this annoyance too... I'd say add Jira issue.
Neeme Praks wrote:
>
> Hi,
>
> While debugging with Tapestry5, I noticed one not-so-nice issue. But
> first, a bit of background.
>
> I usually configure my logging framework (log4j) to log all statements
> for my application at debug level during development. E.g. all log
> records logged to "com.mycompany.myapp" logging category get printed at
> DEBUG level. All other categories are usually at INFO level. This allows
> me to focus on the log statements that I have written and ignore all the
> verbose DEBUG logs of 3rd party libraries.
>
> Back to Tapestry5. I have configured by log4j as usual (my stuff at
> DEBUG level, everything else at INFO level). Although I expect to see
> only the log output produced by MY CODE, I also see some debug output
> produced by Tapestry internals. Seems that Tapestry class enhancement
> code logs to the same log category as the class name being enhanced. And
> the log statements are quite big (documenting the changes being made to
> the original classes), resulting in lots of unwanted noise in my logs.
>
> Example:
> I have a page: com.mycompany.myapp.pages.MyPage
> T5 class enhancement code logs its bytecode manipulation operations to
> log category "com.mycompany.myapp.pages.MyPage", at DEBUG level.
>
> This is not very nice, as I'm totally uninterested in seeing all this
> verbose T5-internal logging.
>
> I understand that it might be beneficial to have that class name as part
> of the logging category (or maybe not), but at the very least, I would
> recommend to add a T5 prefix to all those categories. The log category
> in above example would then become something like
> "org.apache.tapestry.classenhance.com.mycompany.myapp.pages.MyPage".
>
> What do you think?
> Something like this already planned? Or should I add it to JIRA?
>
> Rgds,
> Neeme
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/-T5--DEBUG-level-logging-in-pages-components-tp19535554p19549949.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Re: [T5] DEBUG level logging in pages/components
Posted by Peter Stavrinides <P....@albourne.com>.
+1 for this, its simply too much output for my liking.
----- Original Message -----
From: "Neeme Praks" <ne...@apache.org>
To: users@tapestry.apache.org
Sent: Wednesday, 17 September, 2008 7:01:33 PM GMT +02:00 Athens, Beirut, Bucharest, Istanbul
Subject: [T5] DEBUG level logging in pages/components
Hi,
While debugging with Tapestry5, I noticed one not-so-nice issue. But
first, a bit of background.
I usually configure my logging framework (log4j) to log all statements
for my application at debug level during development. E.g. all log
records logged to "com.mycompany.myapp" logging category get printed at
DEBUG level. All other categories are usually at INFO level. This allows
me to focus on the log statements that I have written and ignore all the
verbose DEBUG logs of 3rd party libraries.
Back to Tapestry5. I have configured by log4j as usual (my stuff at
DEBUG level, everything else at INFO level). Although I expect to see
only the log output produced by MY CODE, I also see some debug output
produced by Tapestry internals. Seems that Tapestry class enhancement
code logs to the same log category as the class name being enhanced. And
the log statements are quite big (documenting the changes being made to
the original classes), resulting in lots of unwanted noise in my logs.
Example:
I have a page: com.mycompany.myapp.pages.MyPage
T5 class enhancement code logs its bytecode manipulation operations to
log category "com.mycompany.myapp.pages.MyPage", at DEBUG level.
This is not very nice, as I'm totally uninterested in seeing all this
verbose T5-internal logging.
I understand that it might be beneficial to have that class name as part
of the logging category (or maybe not), but at the very least, I would
recommend to add a T5 prefix to all those categories. The log category
in above example would then become something like
"org.apache.tapestry.classenhance.com.mycompany.myapp.pages.MyPage".
What do you think?
Something like this already planned? Or should I add it to JIRA?
Rgds,
Neeme
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org