[
https://issues.apache.org/jira/browse/MYFACES-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13853358#comment-13853358
]
Leonardo Uribe commented on MYFACES-3817:
-----------------------------------------
The patch is "technically correct" but I have already explained the reasons why
a solution will not work. The fix will only be marginally meaningful on server
side state saving, because there is no way to update the view state token on
client side state saving.
In few words: the state stored in the component tree is only meaningful as long
as the view is active. If the user requires something else to keep the state
longer, he/she will use managed beans.
In other words, the state of the application, usually stored on managed beans
is one thing, and the state of the "screen" is another. Nobody has ever
complained about this issue because it is not an issue. This issue should be
closed as invalid.
> ajax redirect/navigation loosing state information when changes are executed
> with redirect/navigation
> ------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-3817
> URL: https://issues.apache.org/jira/browse/MYFACES-3817
> Project: MyFaces Core
> Issue Type: Bug
> Components: General
> Affects Versions: 2.2.0-beta
> Environment: Windows 8
> Reporter: Dora Rajappan
> Attachments: processstate.patch
>
> Original Estimate: 0.8h
> Remaining Estimate: 0.8h
>
> Ajax redirect/navigation loosing state information when changes are executed
> with redirect. This can be addressed
> #1 By putting a flag in redirect and write it in response after save state
> in rendering phase.
> #2 This behaviour true for redirect via navigation handler. In render phase
> it goes to response complete and state saving is avoided. When its a redirect
> not make the response complete true and flag it so that in rendering phase
> state is saved.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
