tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <>
Subject Re: Want to customise the tomcat's session logic
Date Sat, 07 Nov 2009 01:44:55 GMT
Hash: SHA1


On 11/2/2009 5:06 AM, S Arvind wrote:
> Basically my requirement is ability to control the session
> sharing in browser. Till now we maintained each application as different
> context but pointing to same doc-base. So different web application will be
> running on a same code to control the session sharing between different
> application.

I don't believe that deploying the same webapp multiple times into
different contexts has any effect on session sharing: Tomcat will treat
them as different webapps and no session sharing will occur unless you
have taken other steps to share sessions between contexts.

> But now we want to run in same context as one application but
> control the session sharing.

So... do you mean that you want to deploy one web application (into a
single context), but you want to separate certain parts of the session
into different "areas" of the webapp?

> So i planned to customise session creation n
> management of the tomcat to our requirements to add some value to
> *path* attribute in session. Is this possible?

To my knowledge, there is no "path" attribute in the session. Are you
proposing that you add one?

Modifying Tomcat's session management code is probably going to lead you
down a path that leads to insanity: the APIs are not (officially)
stable, there is no standard, etc.

I suspect there is a better way to accomplish what you want to do... I
just don't really understand what you want to do. Instead of speaking in
generalities, why not give us a use case?

- -chris
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla -


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message