LiftSession is bound to HttpSession through HttpSessionBindingListener
and HttpSessionActivationListener
This means that when the HTTP session terminates LiftSession will also
terminate. To verify your SessionVar that the session was purged you
can implement
override protected def onShutdown(session: CleanUpParam): Unit = {
...
}
where in case of SessionVar the session parameter is really a
LiftSession.
The LiftSession timeout is given by
HttpSession.getMaxInactiveInterval ... if that period is exceeded the
LiftSession is unbound from the HttpSession. Does not necessary means
that the HttpSession is removed by container ust that LiftSession is
terminated.
But is the problem the fact that HttpSession expired but you still had
the context in the SessionVar?
Br's,
Marius
On Jul 1, 12:47 pm, Ewan <ehar...@gmail.com> wrote:
> I have recently started using a SessionVar and am quite happy to have
> the session wiped after some predefined interval. As an experiment I
> changed the session timeout in the web.xml a la Java Servlets but this
> had no effect running on jetty and since I have read that a SessionVar
> is not just a wrapper around javax.servlet.http.HttpSession. My
> question is then how can I configure the timeout interval?
>
> -- Ewan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en
-~----------~----~----~----~------~----~------~--~---
