Thank you for your suggestions! I will figure it out an post my
experiences.. 

Felix

> -----Original Message-----
> From: Pernoud Aurelien [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, October 14, 2003 10:47 AM
> To: Jetspeed Users List
> Subject: RE: how to pass informations from portlet A to portlet B?
> 
> 
> 
> Holger Dewes a ecrit :
> > 
> > Hello,
> > 
> > that's a common question, it seems. Basically, you don't send the 
> > information, because you cannot guarantee that portlet A is 
> processed 
> > before portlet B. Instead, you let portlet B analyze the 
> request and 
> > fetch the information it needs to display. Anyway, that's 
> how I do it.
> > 
> > Cheers
> 
> You can use an action that will be processed before 
> everything else, so that your context (e.g user session) is 
> ok, and then display portlet information from context, and 
> not from request. IMHO I find it hasardous to change the 
> content of a portlet based on the request object... just my 2 cents ;)
> 

Yes, but this has to be a Turbine action (right?), and then you are
outside of Jetspeed (you cannot access portlet specific information).
And in the end, everything is based on request. But I guess it is a
matter of taste.

(I would _love_ for the portlet actions to be executed before the actual
rendering phase. It is a pity that you can only do that with pure
Turbine actions.)

Cheers
-- 
Holger Dewes


---------------------------------------------------------------------
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]

Reply via email to