sharing session information across webapps

["Anten, Andrew" <An...@mmtenergy.co.uk>]

> what is the prefered mechanism for sharing session information across web
> applications - for example user properties (name, privileges etc).
> anything i pop into the session object is only available to a single web
> application.
> 
> thanks.
> 
> Andy A
> 
> 

Re: sharing session information across webapps

[Eric Ngai <er...@starsolutions.com.my>]

I guess you have to create a user bean which you will user the
<jsp:userBean> in all of your web application. This bean will be general
across different web application, at leass under the Tomcat.

Regards,
Eric Ngai
Star Solutions
Malaysia

----- Original Message -----
From: "Anten, Andrew" <An...@mmtenergy.co.uk>
To: <ge...@jakarta.apache.org>
Sent: Wednesday, May 17, 2000 4:01 PM
Subject: sharing session information across webapps


>
> > what is the prefered mechanism for sharing session information across
web
> > applications - for example user properties (name, privileges etc).
> > anything i pop into the session object is only available to a single web
> > application.
> >
> > thanks.
> >
> > Andy A
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
>

Re: sharing session information across webapps

["Craig R. McClanahan" <Cr...@eng.sun.com>]

"Anten, Andrew" wrote:

> > what is the prefered mechanism for sharing session information across web
> > applications - for example user properties (name, privileges etc).
> > anything i pop into the session object is only available to a single web
> > application.

The "preferred approach" to sharing across web applications is to use any or
all of EJBs, a JDBC-accessed database, JNDI-accessed directory servers, shared
files, or other similar mechanisms external to the servlet container.  You will
*not* be able to count on using things like Singletons, because most
2.2-compatible servlet containers establish separate class loaders for each web
application.

>
> >
> > thanks.
> >
> > Andy A
> >
> >
>

Craig McClanahan