myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabrielle Crawford (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (TRINIDAD-1642) Trinidad 2 - server side state saving does not work
Date Wed, 18 Nov 2009 22:54:39 GMT

    [ https://issues.apache.org/jira/browse/TRINIDAD-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779714#action_12779714
] 

Gabrielle Crawford commented on TRINIDAD-1642:
----------------------------------------------

that should be 
 our own responseStateManager which does not wrap the RI's responseStateManager 

> Trinidad 2 - server side state saving does not work
> ---------------------------------------------------
>
>                 Key: TRINIDAD-1642
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1642
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>            Reporter: Gabrielle Crawford
>            Assignee: Gabrielle Crawford
>
> Server side state saving is not working in Trinidad 2.0, instead of writing a token to
the client the full state is written to the client.
> In Trinidad we have 
> * our own stateManager which wraps the RI's state manager. 
> * our own responseStateManager which does not wrap the RI's state manager
> For server side state saving we delegate to the RI's state manager.  In JSF 1.2 the RI's
stateManager handled saving the state on the session for server side state saving. So server
side state saving worked in Trinidad 1.2.
> In JSF 2.0 the StateManager no longer handles server side state saving, now the ResponseStateManager
handles server side state saving. Trinidad's CoreResponseStateManager just writes out whatever
state it was given, so it writes out the full state instead of writing out a token and saving
the state in the session.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message