You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org> on 2008/10/27 16:06:44 UTC

[jira] Reopened: (TRINIDAD-1135) Flush Cached Model for UIXCollection during broadcast

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

Matthias Weßendorf reopened TRINIDAD-1135:
------------------------------------------


> Flush Cached Model for UIXCollection during broadcast
> -----------------------------------------------------
>
>                 Key: TRINIDAD-1135
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1135
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions:  1.2.8-core, 1.2.9-core
>         Environment: All
>            Reporter: Venkata Guddanti
>            Assignee: Matthias Weßendorf
>             Fix For: 1.0.9-core, 1.2.9-core
>
>         Attachments: trunk.patch
>
>
> If a UIXCollection component is used as a stamp inside another UIXCollection. The model for the collection can go stale during the broadcast of messages.  This is because the model in the stamped UIXCollection could be pointing to the wrong one because of the stamp state processing during the decode/validate/update phase. The fix is to make sure that the stamped collection is using the right model based on the stamp state of the parent collection.  This is done by simply calling _flushCachedModel(); at the beginning of the broadcast.

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