[jira] [Closed] (TAP5-1391) Component event and render exceptions should be routed through a special service to make customization easier

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1391.
--------------------------------------

    Resolution: Won't Fix

Still no idea exactly what this would look like.

> Component event and render exceptions should be routed through a special service to make customization easier
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1391
>                 URL: https://issues.apache.org/jira/browse/TAP5-1391
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.3
>            Reporter: Howard M. Lewis Ship
>
> Currently, you can override the RequestExceptionHandler service, but it lacks a lost of context about what was going on at the time of the exception.
> It would be nice if there was a public, overridable service that was invoked as a kind of exception factory for components.
> What my client is looking for is a more succinct way of gracefully recovering from corrupted data in the request path and query parameters (even if there's a malicious user doing so).



--
This message was sent by Atlassian JIRA
(v6.2#6252)