FacesMessage I18N keys are evaluated differently between "redirect" and "render" navigations -------------------------------------------------------------------------------------------- Key: JBSEAM-3147 URL: http://jira.jboss.com/jira/browse/JBSEAM-3147 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.0.2.SP1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.0.3.GA When using FacesMessages.addFromResourceBundle() message resolution is deferred until after the phase it was added in. Though I'm not exactly sure why it is done this way it is causing problems with "render" vs "redirect" navigations. In the case of a "render" the Pages component changes the current viewID prior to the end of the phase. So when the FacesMessages component processes it's FacesMessages at the end of the phase the viewId is going to be different than what it would be for a "redirect". This can be a problem if you are using Seam Page bundles. IMO the message really should come from the page where the action was invoked not the destination page. If the FacesMessage component defers FacesMessage creation because it wants to do interpolation after the phase is complete perhaps we can change FacesMessages to immediately look up the message key and then lazily interpolate that message? I can go ahead and fix this if nobody has an objection. Mike -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira