You can implement a ContextListener that persists your Vector
when the Context is shutdown.
A quite dirty trick would be to store a reference to the
Vector in each session and let tomcat do the work for you.
> -Ursprüngliche Nachricht-
> Von: Mark O'Driscoll [mailto:[EMAIL PROTECTED]]
>
See below
> -Ursprüngliche Nachricht-
> Von: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 14. August 2002 14:59
> An: Tomcat Users List
> Betreff: RE: How to keep track of sessions
>
> Sessions are not meant to be persisted across server restarts.
>
Obviously other
E.G. if you want to implement a session monitor.
Depending on the kind of information you want to
display it gets at sime point annoying to to copy
everthing from the session to a store and to remove
it from the store when the session ends.
- More code = more possible error, less perfomance
See below:
> -Ursprüngliche Nachricht-
> Von: Shapira, Yoav [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 14. August 2002 16:06
> An: Tomcat Users List
> Betreff: RE: How to keep track of sessions
>
> More code, yes. But I think the SessionInfo-type objects would be
> trivial. The m
I think you make it a bit to comlicated.
The session is invalidated automatically by tomcat.
(See in web.xml)
The only thing that you have to do is implement a
HttpSessionBindingListener store an instance of
this class in the session.
What job are you talking about? Do you start an
operation
Hi,
Does this mean like implementing a ActionListener
interface in swing, once i write a class which
implements this listener automtically events will be
caught when a new session is created or session is
getting invalidated...
In AS/400 when ever i create a user login, there is
job which is sta
ROTECTED]]
> Gesendet: Mittwoch, 14. August 2002 17:48
> An: Tomcat Users List
> Betreff: Re: AW: How to keep track of sessions
>
>
> Hi,
> Does this mean like implementing a ActionListener
> interface in swing, once i write a class which
> implements this listener
