This one is easy but not very intuitive. Lets say you navigate from one
page to another and then hit the back button. When you then try to
resubmit the previous page, there is no view state corresponding to the
token unless you've saved more then one.
This setting allows you to configure how many different tokens are
active at any given time..
Scott
hbMailingList wrote:
Hello again :-)
I'd really like to understand this setting, because I'm worried that I'm
missing something fundemental.
I guess another way I can ask the question is:
- why/when would it be necessary to have more than one view in the session?
Thanks in adv.
hbMailingList wrote:
Hello, I’m thinking of setting javax.faces.STATE_SAVING_METHOD to
server...
I’m wondering what is the right number for NUMBER_OF_VIEWS_IN_SESSION?
I'm guessing that the default is 20, and I’m wondering why would I want to
have more than 1 view in the session?
For example, let’s say I have 5 pages…5 views. The user can see only one
view at a time. So when she moves from page 1 to page 2, why would I need
the view for page 1, in the session? Doesn’t the framework recreate the
view & its component tree once she visits page 1 again?
My understanding was that if the user navigates to a page and it is not a
post-back the view is created from scratch.
I think I’ve misunderstood something, could you please provide me with
some examples, in which I’d need more than one view in the session.
Thanks in advance
