You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mike Kienenberger (JIRA)" <de...@myfaces.apache.org> on 2006/01/10 17:56:23 UTC
[jira] Closed: (MYFACES-1018) PhaseListener That Persists Messages
After Redirects
[ http://issues.apache.org/jira/browse/MYFACES-1018?page=all ]
Mike Kienenberger closed MYFACES-1018:
--------------------------------------
Resolution: Duplicate
Let's keep this in MYFACES-516.
I'd rather not see a phase-listener solution since there are ordering issues with phase-listener execution.
MYFACES-516 has a non-phase-listener solution proposed.
> PhaseListener That Persists Messages After Redirects
> ----------------------------------------------------
>
> Key: MYFACES-1018
> URL: http://issues.apache.org/jira/browse/MYFACES-1018
> Project: MyFaces
> Type: New Feature
> Components: General
> Reporter: Dustin Bruzenak
> Attachments: JsfMessagePhaseListener.txt
>
> Currently when JSFMessages are added to the FacesContext those messages are lost when a redirect is issued. This is a problem for a handler that does some validation that adds messages and then returns a navigation case that has a redirect.
> A PhaseListener can be written that will persist the current JSFMessages in the user's session and then reloads them into the FacesContext on the next request. Since the application will almost never want to add messages to the context and have them immediately be lost, the presence of this listener would help ensure that the message manager matches the expected result.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira