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)" <ji...@apache.org> on 2010/12/27 22:52:45 UTC

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

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.0
            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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.