[
https://issues.apache.org/jira/browse/EXTCDI-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994369#comment-12994369
]
Marcus Büttner commented on EXTCDI-131:
---------------------------------------
Ok, I've think I found the problem.
The WindowContextManagerObserver sets the new viewId after RestoreView
(PhaseEvent). MyFaces does a visitTree when creating view tree. Some components
like UIRepeat touch the model before this WindowContextManagerObserver is
called for setting the new viewId. Therefore the
ViewAccessConversationExpirationEvaluator says that the scope is expired.
I can adjust the problem if I use a <ui:repeat> on page1.
> Lost ViewAccessScope when re post action with navigation
> --------------------------------------------------------
>
> Key: EXTCDI-131
> URL: https://issues.apache.org/jira/browse/EXTCDI-131
> Project: MyFaces CODI
> Issue Type: Bug
> Reporter: Marcus Büttner
> Assignee: Mark Struberg
>
> Post on page 1 calls an action with navigation to page 2. Press reload to
> trigger a (re)post then ViewAccessScope get lost.
> ViewAccessConversationExpirationEvaluator#isExpired causes the problem.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
