You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Dora Rajappan (JIRA)" <de...@myfaces.apache.org> on 2013/11/20 18:26:35 UTC

[jira] [Commented] (MYFACES-3817) ajax redirect/navigation loosing state information when changes are executed with redirect/navigation

    [ https://issues.apache.org/jira/browse/MYFACES-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827871#comment-13827871 ] 

Dora Rajappan commented on MYFACES-3817:
----------------------------------------

In order not to loose state change for the redirect/navigation if you save state in execute cycle before overwrite the viewroot the server side state saving remains in good state but with  the client side state saving you simply cannot send two separate viewstate information. And that is the reason the state is not saved in execute. This conflict has to be addressed. Easiest solution is send a viewstate information after state saving and before overwriting viewroot and then save the new view and send the response.  For all responseComplete navigation cases in execute cycle the overwritten view can be saved in execute cycle to avoid ViewExpiredException. And this will not conflict the clientside and serverside state saving.

>  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
>   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#6144)