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 2012/05/07 16:00:53 UTC

[jira] [Commented] (MYFACES-3540) org.apache.myfaces.HANDLE_STATE_CACHING_MECHANICS = false results in client side state saving

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

Leonardo Uribe commented on MYFACES-3540:
-----------------------------------------

That param is for backward compatibility with the old behavior of StateManager in MyFaces. Maybe some change done causes the problem but it is not a big deal, because there are no known cases that requires this behavior (in theory a StateManager wrapper could rely on this behavior).
                
> org.apache.myfaces.HANDLE_STATE_CACHING_MECHANICS = false results in client side state saving
> ---------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-3540
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3540
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: General
>    Affects Versions: 2.1.7
>         Environment: Richfaces 4.2.1 Final, Tomahawk20_1.1.12, Tomcat 6.0.35
>            Reporter: Michael Heinen
>         Attachments: web.xml
>
>
> Setting the parameter org.apache.myfaces.HANDLE_STATE_CACHING_MECHANICS to false results in a blown up view state on client side.
> The content of javax.faces.ViewState is > 10 times larger.
> Comparison:
> HANDLE_STATE_CACHING_MECHANICS = true
>   Request content length: 2369 bytes
>   Response content length: 1849 bytes
> Same operation with HANDLE_STATE_CACHING_MECHANICS = false
>   Request content length: 28095 bytes
>   Response content length: 25783 bytes
> There seems to be something wrong with the state saving.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira