[
https://issues.apache.org/jira/browse/MYFACES-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815158#comment-13815158
]
Leonardo Uribe commented on MYFACES-3817:
-----------------------------------------
I see. Theorically the spec does not handle this case, but it is hard to find a
use case when this could be a problem, because most of the time the component
state is not relevant after an ajax redirect. But it is just the same for
normal POST requests. Once the navigation to a new page is done, the state of
the previous page is not saved, but the next one which is rendered is saved
into the state. The fact is over the time nobody has complained about this
effect, because usually the changes that matters are inside the model. Note
this behavior is not fixable in client side state saving, because the token
cannot be updated on the client side, but theoretically you can send the view
state token with the redirect. I don't think this could be fixed.
> ajax redirect loosing state information when changes are executed with
> redirect
> --------------------------------------------------------------------------------
>
> 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
> Original Estimate: 0.8h
> Remaining Estimate: 0.8h
>
> Ajax redirect 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#6144)
