Hi, David, Thank you for your help. I'm interested in the later solution you mentioned: to store the navigation state on the URL instead of in the session (a Spring configuration)
I don't know what it means. It means a page's URL or a URL inside a portlet refering to itself? If it's the former, and a clean URL can reset all state back, then the problem is solved. So could you please give me some more information, including how to configure? Thank you. Bob 2007/6/1, David Sean Taylor <[EMAIL PROTECTED]>:
On May 30, 2007, at 6:36 AM, Bob Song wrote: > Hi, all > I have got a problem in portlet modes and states. > Suppose I'm visiting Page A now, and all portlets in this page are > in normal mode. Then I maximize one portlet, and go to page B. When > I'm back to page A, that portlet is still in maximum state. I know > it's a nice feature of portal/portlet paradigm, but sometimes users > are customized to see all portlets in the page when they newly > enter this page. > > So I wanna know how to reset the states and modes of all portlets > of a page to the default. > > I think that this function is out of the scope of JSR-168, and > must be a jetspeed feature, if provided. I hope there is a > convenience way to do that. > Right, the spec does not address the concept of "pages" and navigation amongst pages So our solution is to keep navigational state, such as maximized mode for a portlet, persisted in the session Once you logout, the state is lost and the portlets go back to the default window state (normal) and mode (view) I seem to remember someone asking for this feature before Basically what you want is a way to reset the nav state when navigating to a new page We don't have this feature Another option may be to store the navigation state on the URL instead of in the session (a Spring configuration) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
