[jira] Updated: (TRINIDAD-1168) Bug in UIXCollection.invokeOnComponent

["Kamran Kashanian (JIRA)" <de...@myfaces.apache.org>]

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

Kamran Kashanian updated TRINIDAD-1168:
---------------------------------------

    Status: Patch Available  (was: Open)

> Bug in UIXCollection.invokeOnComponent
> --------------------------------------
>
>                 Key: TRINIDAD-1168
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1168
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions:  1.2.8-core
>         Environment: All
>            Reporter: Kamran Kashanian
>             Fix For: 1.2.9-core
>
>         Attachments: trunk1.2.x.patch
>
>
> The UIXCollection.invokeOnComponent method conditionally clears it's model cache by checking for the client id of the component in the request scope. If the client id is not found, (meaning the cache has not been cleared during the current request), UIXCollection clears the cache and puts the client id in the request scope. 
> However, there is a bug in the actual client id that is saved in the request scope when invokeOnComponent is called for a given row in UIXCollection. The wrong client id is saved in the request scope.
> Submitting a fix for this in a 1.2.x patch.
>     

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