[
https://issues.jboss.org/browse/SEAMFACES-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Leathem updated SEAMFACES-168:
------------------------------------
Fix Version/s: 3.1.0.Tracking
Forum Reference:
http://seamframework.org/Community/SeamCatchViewExpiredExceptionAndRedirect
(was:
http://seamframework.org/Community/SeamCatchViewExpiredExceptionAndRedirect)
> Error page navigation after Seam Catch
> --------------------------------------
>
> Key: SEAMFACES-168
> URL: https://issues.jboss.org/browse/SEAMFACES-168
> Project: Seam Faces
> Issue Type: Feature Request
> Components: Conversations
> Affects Versions: 3.0.1
> Environment: JBoss AS6, Mojarra 2.1
> Reporter: Andrew Wheeler
> Fix For: 3.1.0.Tracking
>
>
> It would be nice to annotate a Seam Catch handler with an error page view
> that is restored after the exception has been handled. This should tidy
> (destroy) any active conversation as the view probably can't be restored. It
> could also mark the event as handled (some default behaviour) if it hasn't
> been handled by the exception handler method.
> E.g:
> @ErrorPage("error")
> public void noConversationHandler(@Handles
> CaughtException<NonexistentConversationException> event) {
> messages.info("The view you were editing has expired.");
> }
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
