You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gabrielle Crawford (JIRA)" <de...@myfaces.apache.org> on 2009/11/18 23:54:39 UTC
[jira] Commented: (TRINIDAD-1642) Trinidad 2 - server side state
saving does not work
[ 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.
Re: [jira] Commented: (TRINIDAD-1642) Trinidad 2 - server side state
saving does not work
Posted by Gabrielle Crawford <ga...@oracle.com>.
yes, it looks like the responsibilities of the statemanager vs
responsestatemanager have changed in JSF 2.0.
Thanks,
Gab
Pavitra Subramaniam wrote:
> >> 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.
> Does this change in JSF 2.0, also explain the NPE I am seeing with
> JIRA issue 1639? <http://issues.apache.org/jira/browse/TRINIDAD-1639>
>
> When doing a postback for the simple testcase I created, the
> CoreResponseStateManager actually returned null for getViewState()
> (rather than return the full state), which caused the NPE.
>
> Thanks
> Pavitra
>
> "Gabrielle Crawford (JIRA) wrote:" On 11/18/2009 2:54 PM PT:
>> [ 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.
>>>
>>
>>
Re: [jira] Commented: (TRINIDAD-1642) Trinidad 2 - server side state
saving does not work
Posted by Pavitra Subramaniam <pa...@oracle.com>.
>> 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.
Does this change in JSF 2.0, also explain the NPE I am seeing with JIRA
issue 1639? <http://issues.apache.org/jira/browse/TRINIDAD-1639>
When doing a postback for the simple testcase I created, the
CoreResponseStateManager actually returned null for getViewState()
(rather than return the full state), which caused the NPE.
Thanks
Pavitra
"Gabrielle Crawford (JIRA) wrote:" On 11/18/2009 2:54 PM PT:
> [ 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.
>>
>
>