- Original Message -
From: "Cui Xiaojing-a13339" <[EMAIL PROTECTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Wednesday, June 18, 2003 7:38 PM
Subject: Question about session
> Hello All,
>
> I have used <%@ page session="f
Hello All,
I have used <%@ page session="false" %> to set the page not to join session, but when
I use HttpSession session = request.getSession(false) to get session, I still can get
the session that created before. Do you think it is a correct status? Why? Thanks.
<%@ page session="false" %>
<
CTED]>
To: "Tomcat Developers List" <[EMAIL PROTECTED]>
Sent: Monday, August 12, 2002 5:50 AM
Subject: Question about Session in Tomcat 3.3 -- continued...
> I changed switch "fullReload" in ReloadInterceptor
> from true to false, and sessions are maintained
> through
I changed switch "fullReload" in ReloadInterceptor
from true to false, and sessions are maintained
through context reloading. (Of course, because the old
context remains.) Is there any disadvantage if I set
this way? Anyway fullReload=true is default setting.
Thanks.
Hugh
_
As I tested, when context reloads in Tomcat 3.3.1,
e.g. caused by modification of servlet class, sessions
are lost. Is it true for all Tomcat 3.3.x? Is there
any switch in source code which can change this
behavior and maintain sessions through context
reloading?
Thanks for your help.
Hugh
___