Hi angeloim,
I believe the portlet spec states that all "Action/processAction" requests
must be executed "before" any render(doView) requests within the portal. So
make sure that your "navigator" portlet changes the "location" on your other
portlet only during "Action" requests NOT during render requests. If
you are already doing this and it is not working ... then this might be a
bug in the session handling of the jetspeed portal engine.
- Frank
-Original Message-
From: angeloimm [mailto:[EMAIL PROTECTED]
Sent: Friday, February 04, 2005 03:02 AM
To: Jetspeed Jetspeed
Subject: PLEASE HELP ME Order of action execution
Importance: High
Hi all; i have this scenario:
A page where there are several portlets; the first portlet is a "Navigator"
that shows to me where i am; now this portlet by reading a parameter in the
session (i have used the PageSessionState) reads a xml file where it can be
able to "understand" where we are; now the problem is that this parameter is
setted by another portlet that is shown after this navigator; this means
that the action of this portlet is executed later than the action of
navigator. and this is a problem for me; infact the old value of
parameter in the session is changed after that the navigator portlet has
taken the value... so the navigator is not synchronized with the page where
we are; if i refresh the page (by using F5 for example) all works fine and i
don't have this problem since the PageSessionState works good.
The problem is that i'ld like to call the action of the second portlet and
then the action of navigator; is this possible?
Thanks
Navighi a 2 MEGA e i primi 3 mesi sono GRATIS.
Scegli Libero Adsl Flat senza limiti su http://www.libero.it
-
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]
