Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

Sorry to bug you all again.. I am still seeking a clarification on above points.. if anyone can please enlighten me. Thanks. On Sat, Feb 15, 2014 at 1:29 AM, user 01 user...@gmail.com wrote: Can some one please clarify What is this attributes map otherwise really meant for? Is it to

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

It's just a map to add data - like ViewState. In JSF 2.0 and JSF 2.1, it was used to directly store the ViewScoped beans. Don't know about more internals. 2014-02-21 21:42 GMT+01:00 user 01 user...@gmail.com: Sorry to bug you all again.. I am still seeking a clarification on above points..

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

Can some one please clarify What is this attributes map otherwise really meant for? Is it to maintain JSF internal viewstate ? On Fri, Feb 14, 2014 at 1:31 AM, user 01 user...@gmail.com wrote: Thanks a lot Leonardo for the solution. Played somewhat with it, looks like it'll works for me. The

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

I dont know why how this is so implemented but It is very normal that the user may be busy reading some section of website or be away for 20 minutes, as he comes back interacts with opened pages, how would I make that work without the state ? I think this is a common requirement for any

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

Good suggestion Thomas, For myself I would need this: 1 Hour: Keep session alive with p:poll 1 Hour: Render p:idleMonitor instead and warn for activity and session destroy in x minutes. The switch to a idleMonitor would require that you check the submitted request parameters and this way

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

Karl, p:poll introduces security concerns? Please elaborate/clarify. Thanks. On Feb 13, 2014 3:39 AM, Karl Kildén karl.kil...@gmail.com wrote: Good suggestion Thomas, For myself I would need this: 1 Hour: Keep session alive with p:poll 1 Hour: Render p:idleMonitor instead and warn for

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

It's just that if you just do p:poll every five minutes they are never logged out from activity. This has actually caused us to fail a security screening in the past. 1. Users use security system before leaving office, forgets to logout and the PC does not lock from inactivity either 2. In the

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

Very interesting, Karl, and thanks for the clarification! +1 at the responses on this thread. They interested me, because for security implementation in my app is - 15 minutes session expiration (web.xml) - meta refresh tag in head tag that redirects page to view expired 'page' (got that

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

Thanks a lot Leonardo for the solution. Played somewhat with it, looks like it'll works for me. The data survives session destroys. What is this attributes map otherwise really meant for, to maintain JSF internal viewstate ? Is it safe for me to use it like that ? Looks like a hack infact:) I

Re: How to survive viewscoped beans/viewmap after session destroy (using client side saving)?

Hi In JSF 2.2 it was decided to store view scope beans always in session (take a look at the description of @ViewScoped annotation in the javadoc). But you can just call facesContext.getViewRoot() and use the attribute map. Just remember the values there must be Serializable or implement