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 2013/10/15 23:53:45 UTC

[jira] [Updated] (MYFACES-3723) JSF 2.2: Support parameter javax.faces.SERIALIZE_SERVER_STATE

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

Leonardo Uribe updated MYFACES-3723:
------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0
         Assignee: Leonardo Uribe
           Status: Resolved  (was: Patch Available)

It seems the change was applied at some point. I added the documentation and deprecated the old param. Thanks to Michael Kurz for provide this patch.

> JSF 2.2: Support parameter javax.faces.SERIALIZE_SERVER_STATE
> -------------------------------------------------------------
>
>                 Key: MYFACES-3723
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3723
>             Project: MyFaces Core
>          Issue Type: New Feature
>          Components: JSR-344
>    Affects Versions: 2.2.0
>            Reporter: Michael Kurz
>            Assignee: Leonardo Uribe
>             Fix For: 2.2.0
>
>         Attachments: MYFACES-3723.patch
>
>
> The JSF 2.2 spec defines a new context parameter javax.faces.SERIALIZE_SERVER_STATE. This parameter controls state serialization for server side state saving. As far as I see it, it should be the same as the MyFaces parameter org.apache.myfaces.SERIALIZE_STATE_IN_SESSION.
> Maybe org.apache.myfaces.SERIALIZE_STATE_IN_SESSION can even be deprecated for 2.2?



--
This message was sent by Atlassian JIRA
(v6.1#6144)