[
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
