Question

I understand that t:saveState allows a request scope bean to persist for longer than request scope allows but shorter than session scope bean. You are also able to use t:saveState on an entire bean.

so my question is if you use t:saveState on an entire bean what are the advantage of using t:saveState over having the Bean configured in session Scope?

Also under what conditions do you make the bean request scope and use T:saveState instead of making the bean Session Scope to being with?

Thanks

Answer 1

The bean which is referenced by <t:saveState> will live as long as the view lives. It does basically the same as the new JSF 2.0 view scope does.

This is particularly useful when you’re dealing with data which should live as long as you’re interacting with the same view by returning null or void on action methods. If you would have used the session scope, then multiple views (multiple browser windows/tabs within the same session) would all share the same data. This may have undesireable side effects when the enduser interacts with the page in multiple browser tabs/windows and switches between them. All changes done in one tab would be reflected in the other tab.

The session scope should absolutely only be used for real session scoped data, such as the logged-in user, its preferences, language, etcetera which can safely be shared between multiple browser windows/tabs within the same session.

See also:

• How to choose the right bean scope?