[TRINIDAD-2263] StateManagerImp.saveView should not check current request token

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.1-core
• Fix Version/s: 2.0.2-core, 2.1.0-core
• Assignee: Gabrielle Crawford
• Reporter: Gabrielle Crawford
• Created: 27/Apr/12 22:20
• Updated: 14/Nov/13 22:26
• Resolved: 30/Apr/12 20:19

Description

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