[PORTLETBRIDGE-50] Should Bridge use Lifecycle to RestoreView when restoring from memory cache?

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-alpha
• Fix Version/s: 1.0.0-beta, 2.0.0-alpha
• Component/s: Impl
• Assignee: Michael Freedman
• Reporter: Michael Freedman
• Created: 02/Oct/08 20:56
• Updated: 09/Dec/08 19:03
• Resolved: 09/Dec/08 19:03

Description

Currently the bridge manually restores the view in the first render after an action from memory (because the action can't save the view via faces). By manual I mean it merely sets the viewRoot to the view instead of calling Lifecycle.execute. This means the before/after restoreView phase listeners aren't called. About six months ago we added a hack to the spec/impl to require the before listener be called but withheld the after worried that running it twice in situation where action/render is usually in a single lifecycle could introduce problems. Well we hit use case where either neither of the two or both must be called but not one without the other (Faces demands this behavior).

In discussing this it was raised that maybe we shouldn't have this manual process at all – instead restore the view from memory when necessary as a natural part of the RestoreView phase of executing the lifecycle.

We decided we should try this and determine if there are any side effects.