On Apr 9, 2008, at 3:17 PM, Eric Dalquist wrote:
Jen realized today playing in the 3-RC3 quickstart that if a portlet
allows guest users to change portlet preferences these are persisted
for the guest user and shared between all guest users. We're pretty
sure this same behavior exists in 2.X as well. Since we have a
portlet with preferences on the guest layout in 3.0 we're going to
work out a solution to the problem as follows.
The PortletPreferencesServiceImpl will have some additional options
available via bean properties; first to just not store portlet prefs
for guest users, second to store them in the guest user's session so
they are scoped and disappear at the end of their session, third to
leave the functionality as is.
If this sounds reasonable I'm also wondering how we define who a
guest is. Should the code check IPerson.isGuest() or
IPerson.getSecurityContext().isAuthenticated()?
Am wondering if it also makes sense from a UI perspective to hide the
edit button for portlets when rendered in the guest mode. Does the
idea of customizing preferences even really make sense for guests,
since there's no persistance?
Jason
--
Jason Shao
Director of Open Source Solutions
CampusEAI Consortium
1940 East 6th Street, 11th Floor
Cleveland, OH 44114
Tel: 216.589.9626x249
Fax: 216.589.9639
--
Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions: The
Community Source Way!"
April 27th - 30th, 2008 in St. Paul, Minnesota USA
Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and
more!
Information/Registration at:
http://www.ja-sig.org/conferences/08spring/index.html
Subscribe to the conference blog, The Community Source Way
http://jasig2008.blogspot.com, for news and updates about the event.
Join the Conference networking site at http://ja-sigspring08.crowdvine.com/
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
