Return-Path: 
 <tomcat-user-return-45541-apmail-jakarta-tomcat-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-tomcat-user-archive@jakarta.apache.org
Received: (qmail 98459 invoked by uid 500); 23 Aug 2001 18:40:56 -0000
Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: tomcat-user@jakarta.apache.org
list-help: <mailto:tomcat-user-help@jakarta.apache.org>
list-unsubscribe: <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
list-post: <mailto:tomcat-user@jakarta.apache.org>
Delivered-To: mailing list tomcat-user@jakarta.apache.org
Received: (qmail 98423 invoked from network); 23 Aug 2001 18:40:56 -0000
Received: from rm-rstar.sfu.ca (root@142.58.120.21)
  by h31.sny.collab.net with SMTP; 23 Aug 2001 18:40:56 -0000
Received: from cultus.sfu.ca (cultus.sfu.ca [142.58.101.5])
	by rm-rstar.sfu.ca (8.10.1/8.10.1/SFU-5.0H) with ESMTP id f7NIevp18955
	for <tomcat-user@jakarta.apache.org>; Thu, 23 Aug 2001 11:40:57 -0700 (PDT)
Message-Id: <200108231840.f7NIevp18955@rm-rstar.sfu.ca>
Content-Type: text/plain
Content-Disposition: inline
To: tomcat-user@jakarta.apache.org
From: "Rob S." <rslifka@sfu.ca>
Organization: Student
X-Sender: rslifka@popserver.sfu.ca
Mime-Version: 1.0
Reply-To: "Rob S." <rslifka@sfu.ca>
Date: Thu, 23 Aug 2001 11:40:57 PDT
X-Mailer: SFUwebmail 2.70
Subject: Re: Preserving session variables across contexts
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

>From the servlet specification:

Section 7: Session Scope

HttpSession objects must be scoped at the application / servlet context level. The underlying mechanism, such as the cookie used to establish the session, can be shared between contexts, but the object exposed, and more importantly the attributes in that object, ***must not be shared between contexts.***

It pays to read the spec before designing =/

All I can think of is storing them in a database based on session ID?

- r

On Thu, 23 Aug 2001 14:34:26 -0400 tomcat-user@jakarta.apache.org wrote:
> Hello,
> 
> It is possible to have session variables preserved across Tomcat
> contexts?
> 
> For example,  if a  user  accesses
> 
>  /<hostname>/ABC/somePage.jsp
> 
> and is redirected to=3D20
> 
>  /<hostname>/XYZ/aDifferentPage.jsp
> 
> can the session variables that were present during the first page be
> preserved??   If so, what is the technique needed to achieve this?
> 
> We seem to be losing our session variables in website we are developing
> when we navigate to a different context even though it is on the same
> server.  It will not be convenient for us to put everything under one
> big context so I was hoping to get a solution to this.
> 
> Thanks,
> Keith