[jira] Updated: (TRINIDAD-2045) UIXCollection should release the reference to the model at the very end of processSaveState

["Venkata Guddanti (JIRA)" <de...@myfaces.apache.org>]

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

Venkata Guddanti updated TRINIDAD-2045:
---------------------------------------

    Status: Patch Available  (was: Open)

> UIXCollection should release the reference to the model at the very end of processSaveState
> -------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-2045
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-2045
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions: 1.2.13-core , 1.2.15-core , 2.0.0-beta-3
>            Reporter: Venkata Guddanti
>         Attachments: tableModelRelease-1.2.12.5.patch, tableModelRelease-1.2trunk.patch, tableModelRelease-trunk.patch
>
>
> UIXCollection is internally hanging onto the collectionModel from applications. This is problematic since the application data could be released between requests. The colleciton model is held internally using iState.value and iState.model. 
> This issue was fixed via issue https://issues.apache.org/jira/browse/TRINIDAD-2024.
> However there is code in UIXCollection processSaveState which nulls out and again restores currency(if any) around the saveState call. Unfortunately the call to restore currency could lead to creation of a bogus CollectionModel in UIXTree component. 
> The fix is to move the call to null out the references to iState.value and iState.model at the very end of the processSaveState method.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira