You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Venkata Guddanti (JIRA)" <de...@myfaces.apache.org> on 2009/03/10 21:26:50 UTC

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

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


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.


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

Posted by "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.


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

Posted by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org>.
     [ https://issues.apache.org/jira/browse/TRINIDAD-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Robinson updated TRINIDAD-1420:
--------------------------------------

       Resolution: Fixed
    Fix Version/s:  1.2.12-core
           Status: Resolved  (was: Patch Available)

Patch committed

> 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
>             Fix For:  1.2.12-core
>
>         Attachments: treeTable.patch
>
>
> UIXTreeTable incorrectly persists the "first" attribute to the change manager.  There is already a comment in the code that this 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.