[TAP5-9] Component event requests that fail should still send a redirect (to the exception report page)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 5.0.15
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 15/Mar/07 18:18
• Updated: 02/May/13 02:29
• Resolved: 23/Nov/11 19:06

Description

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.

Issue Links

• depends upon: TAPESTRY-1356 Implement client-side field persistence