You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/09/08 23:30:29 UTC
[jira] Commented: (TAPESTRY-1738) Render debugging output is
incredibly verbose, and should only be output at the TRACE (i.e. more
vebose than DEBUG) logging level
[ https://issues.apache.org/jira/browse/TAPESTRY-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525960 ]
Howard M. Lewis Ship commented on TAPESTRY-1738:
------------------------------------------------
A little checking showed that Log4J prior to 1.2.12 did not support trace level.
> Render debugging output is incredibly verbose, and should only be output at the TRACE (i.e. more vebose than DEBUG) logging level
> ---------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1738
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1738
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.6
>
>
> Currently if you enable debug output of your page class (i.e., to see the runtime code enhancement) you also get the incredibly verbose diagnostics for rendering of the page. That logging should be at trace, not debug. I believe commons-logging didn't properly offer a trace level (it merged verbose and debug together as debug).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org