myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kamran Kashanian (JIRA)" <>
Subject [jira] Updated: (TRINIDAD-1493) Invalid row key in UIXCollection "invokeOnComponent"
Date Mon, 01 Jun 2009 17:01:07 GMT


Kamran Kashanian updated TRINIDAD-1493:

    Status: Patch Available  (was: Open)

> Invalid row key in UIXCollection "invokeOnComponent"
> ----------------------------------------------------
>                 Key: TRINIDAD-1493
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>          Components: Components
>    Affects Versions:  1.2.11-core
>         Environment: All
>            Reporter: Kamran Kashanian
> 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.

View raw message