You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Adam Winer (JIRA)" <de...@myfaces.apache.org> on 2007/07/26 23:00:05 UTC
[jira] Created: (TRINIDAD-132) UIXCollection.invokeOnComponent()
never flushes the model cache
UIXCollection.invokeOnComponent() never flushes the model cache
---------------------------------------------------------------
Key: TRINIDAD-132
URL: https://issues.apache.org/jira/browse/TRINIDAD-132
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.2.1-core
Reporter: Adam Winer
Assignee: Adam Winer
UIXCollection generally flushes the model twice: once at processDecodes(), and again at encodeBegin(), in both cases to handle receiving a new model.
However, if you use invokeOnComponent() to optimize the JSF lifecycle, this fails: processDecodes() never gets called, so the model is never re-fetched.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-132) UIXCollection.invokeOnComponent()
never flushes the model cache
Posted by "Adam Winer (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Winer updated TRINIDAD-132:
--------------------------------
Resolution: Fixed
Fix Version/s: 1.2.2-core
Status: Resolved (was: Patch Available)
Fixed on 1.2.2, plus the 1.2.1.1 branch
> UIXCollection.invokeOnComponent() never flushes the model cache
> ---------------------------------------------------------------
>
> Key: TRINIDAD-132
> URL: https://issues.apache.org/jira/browse/TRINIDAD-132
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.2.1-core
> Reporter: Adam Winer
> Assignee: Adam Winer
> Fix For: 1.2.2-core
>
> Attachments: collection-invoke.patch
>
>
> UIXCollection generally flushes the model twice: once at processDecodes(), and again at encodeBegin(), in both cases to handle receiving a new model.
> However, if you use invokeOnComponent() to optimize the JSF lifecycle, this fails: processDecodes() never gets called, so the model is never re-fetched.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-132) UIXCollection.invokeOnComponent()
never flushes the model cache
Posted by "Adam Winer (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Winer updated TRINIDAD-132:
--------------------------------
Status: Patch Available (was: Open)
> UIXCollection.invokeOnComponent() never flushes the model cache
> ---------------------------------------------------------------
>
> Key: TRINIDAD-132
> URL: https://issues.apache.org/jira/browse/TRINIDAD-132
> Project: MyFaces Trinidad
> Issue Type: Bug
> Affects Versions: 1.2.1-core
> Reporter: Adam Winer
> Assignee: Adam Winer
> Attachments: collection-invoke.patch
>
>
> UIXCollection generally flushes the model twice: once at processDecodes(), and again at encodeBegin(), in both cases to handle receiving a new model.
> However, if you use invokeOnComponent() to optimize the JSF lifecycle, this fails: processDecodes() never gets called, so the model is never re-fetched.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.