[TRINIDAD-1493] Invalid row key in UIXCollection "invokeOnComponent"

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.11-core
• Fix Version/s: 1.2.12-core
• Component/s: Components
• Environment: All
• Assignee: Unassigned
• Reporter: Kamran Kashanian
• Created: 01/Jun/09 16:59
• Updated: 27/Jan/10 08:46
• Resolved: 01/Jun/09 18:04

Description

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.