[
https://issues.apache.org/jira/browse/TRINIDAD-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12786373#action_12786373
]
Matthias Weßendorf commented on TRINIDAD-1642:
----------------------------------------------
B) sounds fine with me, but I see this ticket has already been solved ...
> 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
> Fix For: 2.0.0-core
>
>
> 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.
