[jira] Updated: (TRINIDAD-1420) UIXTreeTable incorrectly persists the first attribute to the changeManager

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

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

Venkata Guddanti updated TRINIDAD-1420:
---------------------------------------

    Status: Patch Available  (was: Open)

> UIXTreeTable incorrectly persists the first attribute to the changeManager
> --------------------------------------------------------------------------
>
>                 Key: TRINIDAD-1420
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1420
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions:  1.2.11-core,  1.2.12-core
>            Reporter: Venkata Guddanti
>            Priority: Critical
>         Attachments: treeTable.patch
>
>
> UIXTreeTable is incorrectly persists the "first" attribute to the change manager.  There is already a comment in the code that this is was incorrectly implemented. Here are the issues with this:
> - There is no attribute in the treeTable called "first". Instead the setter is implemented using a map per path in the tree. So persisting this attribute does not make any sense.
> - Trinidad does not save the "current" child collection row key when it saves "first".  So, when the component is restored,  it will always change the root collection "first" .
> Oracle RCF internally uses the UIXTreeTable and since there is no "first" attribute, the change persistence implemented using Meta Data Storage(MDS) blows up. This fix is critical internally.
> Put the fix in 1.2.11.1, 1.2.11.2 and trunk code paths.

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