Hi Fredrik,
>
> HttpSession session = .;
> session.setAttribute(String nameOfYourObject, Object yourObject);
> Object yourObject = session.getAttribute(String nameOfYourObject);
Surely, this cannot be correct? It would take me some effort to try
sharing attributes between webapps, so I can'
On Tue, 2007-03-13 at 19:34 +0100, Gregor Schneider wrote:
> I guess you're talking about JSSOSessionID-Cookie, right?
Indeed.
> I believe the whole design is not too smart:
>
> Since all webapps are sharing the same session, I'd store the needed
> values as session-attributes (too lazy to look
I guess you're talking about JSSOSessionID-Cookie, right?
I believe the whole design is not too smart:
Since all webapps are sharing the same session, I'd store the needed
values as session-attributes (too lazy to look it up right now, but
should work like
HttpSession session = .;
session.s
Hi List!
We are developing a couple of webapps that need to talk to each other,
and to do that, we have been using HTTP to just fetch certain URLs from
the other webapps to the requesting webapp. To ensure that the
programmatic request is carried out in the context of the user doing the
client req
