[TRINIDAD-1676] ha: provide facility to support putting uicompoenent references into the session

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.12-core
• Fix Version/s: 1.2.14-core
• Assignee: Matthias Wessendorf
• Reporter: Matthias Wessendorf
• Created: 07/Jan/10 08:33
• Updated: 09/Feb/10 08:28
• Resolved: 09/Feb/10 08:28

Description

We repeatedly see the need from customers to provide support to serialize
UIComponents in the HTTPSession. However, the problem is that the
application should not be storing UIComponent instances in the session. For
an explanation of the issue see:
http://www.nabble.com/Serializable-UIcomponents-td19471884.html.

1) A Serialiable UIComponentReference object that can be used to efficiently
find a component instance using a scoped id. The implementation would store
both the scoped id and the UIComponent path (say child index/facet name at
each level, plus names of naming containers traversed) to the component in
question. If we can find the UIComponent using the path, we return it that
way, otherwise we use findComponent and then update the path information for
next time).

2) A Serialiable UIComponentHolder object that ueses a UIComponentReference
but also caches a UIComponent during the lifetime of a request a clears it at
the end of the request or before render response if the viewId changes.