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/03/15 19:20:09 UTC
[jira] Created: (TAPESTRY-1362) Action requests that fail should
still send a redirect (to the exception report page)
Action requests that fail should still send a redirect (to the exception report page)
-------------------------------------------------------------------------------------
Key: TAPESTRY-1362
URL: https://issues.apache.org/jira/browse/TAPESTRY-1362
Project: Tapestry
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.0
Reporter: Howard M. Lewis Ship
When a request, such as a form submission, fails with an exception, we currently render the exception report page within the same request.
We should capture the necessary information (as client persistent properties, once implemented as TAPESTRY-1356), including request headers and session state *within the request which threw the exception*, then send a normal client-redirect to the exception page to present the data.
If nothing else, this will be needed by the time we implement portlets, since you can't fudge the difference between action and render requests inside a portlet container.
--
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] Updated: (TAPESTRY-1362) Action requests that fail should
still send a redirect (to the exception report page)
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1362:
-------------------------------------------
Fix Version/s: 5.0 Next Release
> Action requests that fail should still send a redirect (to the exception report page)
> -------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1362
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1362
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
> Fix For: 5.0 Next Release
>
>
> When a request, such as a form submission, fails with an exception, we currently render the exception report page within the same request.
> We should capture the necessary information (as client persistent properties, once implemented as TAPESTRY-1356), including request headers and session state *within the request which threw the exception*, then send a normal client-redirect to the exception page to present the data.
> If nothing else, this will be needed by the time we implement portlets, since you can't fudge the difference between action and render requests inside a portlet container.
--
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] Commented: (TAPESTRY-1362) Action requests that fail should
still send a redirect (to the exception report page)
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555654#action_12555654 ]
Howard M. Lewis Ship commented on TAPESTRY-1362:
------------------------------------------------
Really, one of the big pieces here is capturing the request information for the request that failed, rather than for the (render redirect) that renders the exception page.
> Action requests that fail should still send a redirect (to the exception report page)
> -------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1362
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1362
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0
> Reporter: Howard M. Lewis Ship
>
> When a request, such as a form submission, fails with an exception, we currently render the exception report page within the same request.
> We should capture the necessary information (as client persistent properties, once implemented as TAPESTRY-1356), including request headers and session state *within the request which threw the exception*, then send a normal client-redirect to the exception page to present the data.
> If nothing else, this will be needed by the time we implement portlets, since you can't fudge the difference between action and render requests inside a portlet container.
--
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] Updated: (TAP5-9) Component event requests that fail should
still send a redirect (to the exception report page)
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-9:
------------------------------------
Summary: Component event requests that fail should still send a redirect (to the exception report page) (was: Action requests that fail should still send a redirect (to the exception report page))
> Component event requests that fail should still send a redirect (to the exception report page)
> ----------------------------------------------------------------------------------------------
>
> Key: TAP5-9
> URL: https://issues.apache.org/jira/browse/TAP5-9
> Project: Tapestry 5
> Issue Type: Bug
> Affects Versions: 5.0.15
> Reporter: Howard M. Lewis Ship
>
> When a request, such as a form submission, fails with an exception, we currently render the exception report page within the same request.
> We should capture the necessary information (as client persistent properties, once implemented as TAPESTRY-1356), including request headers and session state *within the request which threw the exception*, then send a normal client-redirect to the exception page to present the data.
> If nothing else, this will be needed by the time we implement portlets, since you can't fudge the difference between action and render requests inside a portlet container.
--
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