You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org> on 2010/02/09 09:29:28 UTC

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

     [ https://issues.apache.org/jira/browse/TRINIDAD-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Weßendorf resolved TRINIDAD-1676.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.14-core 

> ha: provide facility to support putting uicompoenent references into the session
> --------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1676
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1676
>             Project: MyFaces Trinidad
>          Issue Type: New Feature
>    Affects Versions:  1.2.12-core
>            Reporter: Matthias Weßendorf
>            Assignee: Matthias Weßendorf
>             Fix For: 1.2.14-core 
>
>         Attachments: Trinidad-1676.diff
>
>
> 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. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.