On May 29, 2007, at 2:22 AM, V C, Srivathsan wrote:
Hi David,
Oh Yes, you are right!! The servlet was indeed running under my webapp
context, and not under jetspeed's context. Once the servlet was put
into
the jetspeed's context, the VM was able to read the attributes in the
session. How did I miss that!!!! :O
However, is there any way that I can put some attributes into the
jetspeed session context, from a servlet running under my webapp's
context? I do not want to add a custom servlet into Jetspeed's
webapp as
far as possible, and having a hook into jetspeed webapp's session
context from my webapp would enable me to do that.
We try to separate the class loader and request processing for the
portal from other servlets
The usual way to add attributes is by hooking into the Jetspeed
request pipeline, such as the method described here
https://issues.apache.org/jira/browse/JS2-584
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
