[
https://issues.apache.org/jira/browse/TAPESTRY-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561403#action_12561403
]
Daniel Jue commented on TAPESTRY-1724:
--------------------------------------
This could also be a round-about solution for form submissions that reference
an expired session. Not sure if this happens in Tapestry natively, but when
using Acegi, if you submit a form from an expired session, you will get an
error page after being forced to log in again.
Since Acegi is usually site wide, we would still want to use some kind of
custom URL request filter (tell Acegi to use it in it's config) and strip form
variables.
But it would be nice for any page to grab a hold of an error and handle it in a
page-specific way.
> Way for pages to intercept errors easily
> ----------------------------------------
>
> Key: TAPESTRY-1724
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1724
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> It would be nice if there was a way pages could define an event handler that
> would be notified in the event of an exception while processing the page; it
> should be passed the exception and some indicator (an enum) of where the
> exception occured. This would allow a way for individual pages to handle
> certain exceptions in a specific way.
> A particular use case for this would be handling the case where parameters
> can not be coerced when invoking an activate event handler method, but
> there's quite likely many others.
--
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]
