Hi all,
Thanks for all replies they help me a lot.
Regards
Carlos
Martin Gainty escribió:
Good Morning Eric and Carlos-
Indeed there is a way to enable CrossContext communication via the
CrossContext="true" directive inside the Context tag
<Context path="/pluto" crossContext="true" />
This capability is available from combined engineering staff from Sun
Microsystems and the IBM Corporation.
Tthe specific JSR-168 spec is published at
http://jcp.org/aboutJava/communityprocess/final/jsr168/
For specific implementation details I would encourage you to look at
John Lewis' article available at
http://www.theserverside.com/tt/articles/article.tss?l=ClusteringTomcat
HTH.
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please
notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message ----- From: "Eric Haszlakiewicz"
<[EMAIL PROTECTED]>
To: "Carlos Alonso Vega" <[EMAIL PROTECTED]>
Cc: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Friday, June 02, 2006 9:11 PM
Subject: Re: Retrieve certain session data inside a servlet
On Fri, Jun 02, 2006 at 11:15:03AM +0200, Carlos Alonso Vega wrote:
Bob,
Thanks for the reply. My problem is that the session info I need is not
of the session that makes the request. I need to check other
sessions in
the same context. I can use the request because it is in the same
context, so the manager is the same.
This servlet is called internally from the app, and checks if some
session exists. It is similar to the case of obtaining all active
sessions from one context using the manager inside the servlet code
(findSessions). If someone have this piece of code (or similar), it
will
serve me.
To do something like that you need to do it yourself. i.e. store a
HashTable in the application context, then add and remove sessions to
it when people login and logout, or at some other convinient time.
Of course, this assumes your app isn't running in a distributed
environment.
If it is, then it's impossible to get a session object from a different
JVM. (well, you could serialize it and transfer the data, but it won't
be the same object and it won't be useful for much other than extracting
some info)
eric
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
