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 2008/01/29 01:02:31 UTC
[jira] Created: (TAPESTRY-2097) Render exceptions should identify
the components that are actively rendering
Render exceptions should identify the components that are actively rendering
----------------------------------------------------------------------------
Key: TAPESTRY-2097
URL: https://issues.apache.org/jira/browse/TAPESTRY-2097
Project: Tapestry
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0.9
Reporter: Howard M. Lewis Ship
Assignee: Howard M. Lewis Ship
This can be very handy when figuring out how and where things have gone wrong. Because of how Tapestry's render queue works, it is hard to extract this information from a stack trace or from the debugger.
--
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
[jira] Closed: (TAPESTRY-2097) Render exceptions should identify
the components that are actively rendering
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-2097.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.10
> Render exceptions should identify the components that are actively rendering
> ----------------------------------------------------------------------------
>
> Key: TAPESTRY-2097
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2097
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.9
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.0.10
>
>
> This can be very handy when figuring out how and where things have gone wrong. Because of how Tapestry's render queue works, it is hard to extract this information from a stack trace or from the debugger.
--
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