[PORTLETBRIDGE-213] Portlet 2.0 Bridge: FacesMessages not updated in bridge scope if empty

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0, 3.0.0-alpha
• Fix Version/s: 2.0.1, 3.0.0-alpha
• Component/s: Impl
• Assignee: Michael Freedman
• Reporter: Michael Freedman
• Created: 03/Jun/11 19:15
• Updated: 07/Jun/11 18:14
• Resolved: 07/Jun/11 18:14

Description

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.