It would be a nightmare ;)
Sessions are used to store objects, lots of libs does store in session
various datas.
All objects loaded are linked to their Classloader. So if you store a
org.mycompany.MyData
object under key "SOME_KEY" in session within webapp1 and you do this in
webapp2:
if (session.getAttribute("SOME_KEY") instanceof org.mycompany.MyData){
// We will never get in this block because
// object was created in webapp1 and we are conparing
// object class to the class MyData loaded from webapp2
// unless MyData is in common/lib
}
If you just want to prevent user from loggin in again, use the single
sign-on valve.
http://tomcat.apache.org/tomcat-5.5-doc/config/host.html#Single%20Sign%20On
Eoghan Shields a écrit :
> Hi,
> Is it possible to have a single session which can be used over
> multiple applications on a single server, the basic problem is there
> is multiple webapps running on the same server but when a user logs
> into one, it would be nice to share all their session data so that
> they could switch between applications to avoid
> them having to log in again.
> I have been looking at the documentation and stuff but so far have
> come up blank, was hoping might be able to steer me in the right
> direction.
> Thanks in advance,
> Eoghan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
