> David Sean Taylor wrote: > We correctly keep the render parameters *until* an action on the > targeted portlet is invoked. At that point the render parameters are > cleared for the targeted portlet (only).
Ahhh, so it is by design (of the portlet spec). Hmmm ... am I alone in the "portal/portlet" community in feeling that this behaviour seems counter-intuitive for a web site?!? By "storing" the render parameters until another action is called, you're basically duplicating the functionallity of session variables, no? IMHO navigating off a page should be another use-case where render-parameters should be cleared. This IS how most well-designed web sites behave anyway ... at least in my experience. How else would a user "get back" to the "top" of a portlet that is multi-layered (many views) without being able to click the portal menu that got them to the portlet in the first place? Just my 2 cents. - Frank --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
