Gabrielle Crawford created TRINIDAD-2263:
--------------------------------------------
Summary: StateManagerImp.saveView should not check current request
token
Key: TRINIDAD-2263
URL: https://issues.apache.org/jira/browse/TRINIDAD-2263
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 2.0.1-core
Reporter: Gabrielle Crawford
StateManagerImp.saveView calls _saveAsToken, which in turn calls
_calculateTokenStateSaving. In _calculateTokenStateSaving where we're checking
if the last view state token starts with a "!" in case setPerViewStateSaving
was called on the previous page. The problem is that we shouldn't care if the
token from the last page used client or server state saving in
StateManagerImp.saveView
--
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
