[
https://issues.jboss.org/browse/GTNPORTAL-836?page=com.atlassian.jira.plu...
]
Rich Raposa commented on GTNPORTAL-836:
---------------------------------------
My interpretation of the following paragraph out of JSR286 is that each user of a portlet
has their own specific preferences stored in the JCR. In fact, the spec specifically
states that there is no API for NOT making them user specific.
"Portlet Specification assumes preference attributes are user specific, it does not
make any
provision at API level or at semantic level for sharing preference attributes among
users,
but enables sharing of preferences and different levels of portlet entities (see Section
5.3.1). If a portal/portlet-container implementation provides an extension mechanism for
sharing preference attributes, it should be well documented how the sharing of preference
attributes works. Sharing preference attributes may have significant impact on the
behavior of a portlet. In many circumstances it could be inappropriate sharing attributes
that are meant to be private or confidential to the user."
javax.portlet.PortletPreferences not user-specific
--------------------------------------------------
Key: GTNPORTAL-836
URL:
https://issues.jboss.org/browse/GTNPORTAL-836
Project: GateIn Portal
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Environment: GateIn 3.0.0 CR1 with JBoss AS 5.1.0 JDK6 (zip) on Windows XP
(gatein-sample-portal removed).
Reporter: Hardy Massen
Fix For: 3.3.0-GA
Attachments: UserPref.war
javax.portlet.PortletPreferences are not user-specific. All users share the same set of
Preferences.
Attached a test-portlet-war.
1. Deploy
2. Login as John, save a User-Preference with test-portlet
3. Login as Mary, save a User-Preference with test-portlet
=> John now sees the User-Preference of Mary and viceversa
This contradicts the Spec.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira