On 08/01/2010 07:18, Arnab Ghosh wrote:
I found that session created in A and B are different and invisible to each
other. But the session ID is same. I want to know is there any chance of
overriding existing session in context B?? Is it a mere coincidence or is
there any logic behind this
Dear Friends,
In that case - suppose a session with a *D52869941C38BC234**CD9A940429C403A
* Id is already present in context B (forwarded from context C ). Now a new
request with same jsessionID came to context A . Then context A forwarded
the request to context B .then will it override the
On 08/01/2010 09:44, Arnab Ghosh wrote:
Dear Friends,
In that case - suppose a session with a *D52869941C38BC234**CD9A940429C403A
* Id is already present in context B (forwarded from context C ). Now a new
request with same jsessionID came to context A . Then context A forwarded
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Arnab,
On 1/8/2010 5:34 AM, Arnab Ghosh wrote:
Can I disable the session creation in context A and C?
Sure: make sure all your JSPs have session=false in their headers, and
make sure that you call request.getSession(false) and check for NULL
every
From: Arnab Ghosh [mailto:gh...@glenwoodsystems.com]
Subject: Cross Context Session Creation-
Now I want to know while forwarding a request from A to D ,
whether session will go from A to D or a new session will
be created under D.
To quote from 7.3 of the servlet spec (which you should
Dear Friends,
*To quote from 7.3 of the servlet spec (which you should read):
HttpSession objects must be scoped at the application (or servlet context)
level. The underlying mechanism, such as the cookie used to establish the
session, can be the same for different contexts, but the object
