You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2011/05/31 21:03:47 UTC

[jira] [Resolved] (MYFACES-3162) AJAX Broken when State Caching Mechanics turned off

     [ https://issues.apache.org/jira/browse/MYFACES-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leonardo Uribe resolved MYFACES-3162.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.1
                   2.0.7
         Assignee: Leonardo Uribe

> AJAX Broken when State Caching Mechanics turned off
> ---------------------------------------------------
>
>                 Key: MYFACES-3162
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3162
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.0.6
>         Environment: MyFaces 2.0.6, RichFaces 4.0.Final, Tomcat 6
>            Reporter: James G
>            Assignee: Leonardo Uribe
>             Fix For: 2.0.7, 2.1.1
>
>         Attachments: MYFACES-3162-1.patch
>
>
> When the web configuration param "org.apache.myfaces.HANDLE_STATE_CACHING_MECHANICS" is set to false, after the first ajax call, all further ajax calls fail.  The failure occurs with a ViewExpiredException on the next ajax call.  The reason is that the sequence number part of the view state is being lost during the first ajax call.  (See HtmlResponseStateManager.getViewState() where baseState is lost when isHandlingStateCachingMechanics(facesContext) returns false.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira