myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Weßendorf (JIRA) <...@myfaces.apache.org>
Subject [jira] Updated: (TRINIDAD-1135) Flush Cached Model for UIXCollection during broadcast
Date Sat, 28 Jun 2008 16:15:47 GMT

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

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

       Resolution: Fixed
    Fix Version/s: 1.0.9-core
           Status: Resolved  (was: Patch Available)

Fixed it on the JSF 1.1 trunk as well....

Thanks for the patch

> 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,  1.2.8-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.


Mime
View raw message