[
https://issues.apache.org/jira/browse/PLUTO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Nicklous resolved PLUTO-615.
----------------------------------
Resolution: Won't Fix
outside the current scope of Pluto
> Allow per-page PortletPreferences to be specified
> -------------------------------------------------
>
> Key: PLUTO-615
> URL: https://issues.apache.org/jira/browse/PLUTO-615
> Project: Pluto
> Issue Type: Improvement
> Components: portal driver
> Affects Versions: 2.0.3
> Reporter: Tom Wirschell
>
> I'm trying to develop a web content portlet to use, amongst other portals, on
> Pluto.
> The use-case is that you can have multiple instances of this portlet on any
> given page which will give some form of text output to the user as configured
> by the admin. But in the current pluto-portal-driver.xml you can only name a
> given portlet within its context. You cannot provide additional information
> to the portlet at this level.
> The DefaultPortletPreferencesService generates a key to look up portlet
> preferences but this key consists of only the portlet name and the remote
> user's name. This key should be expanded with the page the portlet is on and
> the instance of the portal within the page (which means the
> portal-pluto-driver-config.xsd needs to be expanded with something like an
> optional "instance" field).
> If there's a better way to improve on this situation, I'm all ears.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
