Hi Folks:
Don't really know much yet about this... I've implemented sensitive-form
resubmissions by way of tokens within actions but have a question about
when a session times out...
Under Apache (I don't know where yet), I suspect there's a timer/variable
in some configuration file that says how long a session bean is valid
without any hits before it times out. I also think one can call
explicity "request.getSession().invalidate()" which does the same thing but
affects all session beans....
So here's my question(s):
- Anyone have any advice on how to deal with this programatically?
- When session beans do "timeout" or become "invalid", are they
automatically cleaned up by the system? So in essance if I have a bean
called "fooBean" that I added via (request.getSession().setAttribute
("fooBean", fooBeanInstance) AND if the session automatically times out
(without me calling request.getSession().removeAttribute("fooBean")), does
the tomcat contain remove "fooBean" from the session scope or will it still
be there if I call "request.getSession().setAttribute("fooBean")"....
I'd like to understand a little bit more on how best to handle/deal with
situations where the session becomes invalid() or times out. What happens
to all the beans/data contained for that session. With struts, do all
formbeans with session scope become defunct?
thanks,
Theron
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
