myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dustin Bruzenak (JIRA)" <>
Subject [jira] Commented: (MYFACES-1018) PhaseListener That Persists Messages After Redirects
Date Tue, 10 Jan 2006 17:15:20 GMT
    [ ] 

Dustin Bruzenak commented on MYFACES-1018:

No problem. This is a solution to an issue we had internally that I figured I'd post for group

I agree that this is a application implementation concern as opposed to something that should
be included in the 'core' JSF implementation. I think that if the phase ordering issues get
resolved putting something like this in a PhaseListener makes sense from the perspective that
the JSF messaging is a JSF specific task and so should have a JSF specific solution. Where
to put it, on the other hand, is purely a packaging concerned and I'm not familiar enough
with the project to make that choice/suggestion.

> PhaseListener That Persists Messages After Redirects
> ----------------------------------------------------
>          Key: MYFACES-1018
>          URL:
>      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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message