[
https://issues.apache.org/jira/browse/TRINIDAD-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Robinson updated TRINIDAD-1493:
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.12-core
Status: Resolved (was: Patch Available)
Applied patch
> Invalid row key in UIXCollection "invokeOnComponent"
> ----------------------------------------------------
>
> Key: TRINIDAD-1493
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1493
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 1.2.11-core
> Environment: All
> Reporter: Kamran Kashanian
> Fix For: 1.2.12-core
>
> Attachments: uixcollection1.2.11.3.patch
>
>
> Under certain circumstances, UIXCollection tries to set an invalid row key
> in the underlying collection model.
> On a PPR postback, the "invokeOnComponent" logic in UIXCollection parses
> the target clientId string and assumes that the string following the
> NamingContainer.SEPARATOR_CHAR is a valid client token (with a corresponding
> row key). The parsed token is then used to set a "current" row key in the
> collection model before calling "invokeOnComponent" on the children of the
> UIXCollection.
> If a child component inside a table/column header/footer facet is PPRed,
> there is no valid token in the clientId and the above logic breaks and tries
> to set an invalid row key in the collection model.
> Attaching a 1.2.11 patch to fix the issue. The fix checks for a valid row
> key before calling setRowKey on the underlying model.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
