On Oct 30, 2007, at 2:58 PM, Eric Dalquist wrote:
Persisting portlet state between logins has never been implemented
in uPortal. Portlet state/mode data is different than channel
attribute parameters and because of this mismatch the parameter
persistence functionality in uPortal doesn't provide a solution to
this.
Dustin S. wrote:
Hi,
I'm having problems getting the window state of JSR-168 portlets
to persist. If I click the minimize button on the portlet the
portlet is minimized, however logging out of uPortal and logging
back in shows the portlet as unminimized.
In the case of minimizing, you might be able to get away with it if
you were willing to assume some constraints.
http://osdir.com/ml/java.jasig.uportal/2006-07/msg00031.html has some
notes on getting the minimized attribute to stick. If you wanted to
edit the theme transform to not display any content for portlets (I
think there's an isPortlet attribute) then you could probably get
uPortal to minimize the chrome, and hide the content. You'd probably
still incur the cost of the render cycle however, but if that wasn't
to high it might be viable.
Other functionality is more problematic. I'm going to cc: this
conversation onto up-dev -- Eric -- what do you think about having
portlets expose more info about their state into the XML and driving
the state of controls off off that info?
Jason
--
Jason Shao
Application Developer
Rutgers University, Office of Instructional & Research Technology
v. 732-445-8726 | f. 732-445-5539 | [EMAIL PROTECTED] | http://
jay.shao.org
--
You are currently subscribed to [email protected] as: [EMAIL
PROTECTED]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/uportal-dev
