I agree with Holger Dewes since all portlets share the same request object, and what the portlet will render depends upon other portlets how to deal with their content.
sophy ----- Original Message ----- From: "Holger Dewes" <[EMAIL PROTECTED]> To: "'Jetspeed Users List'" <[EMAIL PROTECTED]> Sent: Thursday, July 31, 2003 12:15 AM Subject: RE: communication between portlets > -----Original Message----- > From: Ender Hikmet KILI�O�LU [mailto:[EMAIL PROTECTED] > Sent: Wednesday, July 30, 2003 6:12 PM > To: Jetspeed Users List > Subject: YNT: communication between portlets > > > but the order is important > message sender applet must be run before receiver on other > case it wont work > Actually, I see it the other way around: because (in general) you have no influence over the rendering order of the portlets, you have to make sure that order does _not_ matter. That's why I said, portlet B has to check the request, if portlet B is the one to display the result of the request. Then it won't matter whether portlet A has been rendered already. Of course, portlet A could also be influenced by the request. In that case you either let both portlets create their result independently or let whoever gets the result first put it in the request for the others. Anyway, that's how I do it :-) Cheers -- Holger Dewes --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
