tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julio C. Rivera" <juc...@ya.com>
Subject Re: HttpSessionListener.sessionDestroyed
Date Fri, 05 Sep 2003 23:09:01 GMT
 From the "Tapestry Developers Guide" 
(http://jakarta.apache.org/tapestry/doc/DevelopersGuide/coding.visit.html):
   "... the visit object is serialized with the engine ..."
 From the "Tapestry Users Guide" 
(http://jakarta.apache.org/tapestry/doc/TapestryUsersGuide/state.engine.html):
" ... The engine is itself stored as an HttpSession attribute. ..."

About when the session expires:
See the valueUnbound method in AbstractEngine 
(http://jakarta.apache.org/tapestry/doc/api/org/apache/tapestry/engine/AbstractEngine.html#valueUnbound(javax.servlet.http.HttpSessionBindingEvent).

I *think* it's called when the engine is unbound from the session.

I hope this helps.
    Julio.

At 23:57 05/09/2003 +0300, you wrote:
>Hi,
>
>I am trying to perform some action when the session expires: record a
>user auto-logout event. I need to find the Visit object somehow. Can
>someone tell me how it is the Visit stored? Is it a session attribute?
>Is there another way to achieve this goal.
>
>Thanks, Len


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org


Mime
View raw message