[
https://issues.apache.org/jira/browse/PORTLETBRIDGE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Freedman resolved PORTLETBRIDGE-213.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0-alpha
2.0.1
cached messages no longer saved if current request didn't generate any.
> Portlet 2.0 Bridge: FacesMessages not updated in bridge scope if empty
> -----------------------------------------------------------------------
>
> Key: PORTLETBRIDGE-213
> URL: https://issues.apache.org/jira/browse/PORTLETBRIDGE-213
> Project: MyFaces Portlet Bridge
> Issue Type: Bug
> Components: Impl
> Affects Versions: 2.0.0, 3.0.0-alpha
> Reporter: Michael Freedman
> Assignee: Michael Freedman
> Fix For: 2.0.1, 3.0.0-alpha
>
>
> The Bridge manages FacesMessages in its scope (so Messages generated during
> an action are carried forward to the render). Unfortunately its impl of
> saveFacesMessageState only writes the FacesMessages data structure into the
> scope if there are messages in the current FacesContext. Because the
> resource code copies forward (merges) all scope attributes that aren't there
> at the end of the resource request, we are inadvertently copying forward the
> old set of FacesMessages (rather then the new empty set). Fix is to always
> put the FacesMessages data structure into the scope even if its empty.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
