portals-pluto-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Wirschell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PLUTO-615) Allow per-page PortletPreferences to be specified
Date Fri, 29 Jun 2012 10:37:43 GMT

    [ https://issues.apache.org/jira/browse/PLUTO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403820#comment-13403820
] 

Tom Wirschell commented on PLUTO-615:
-------------------------------------

There are of course many ways in which Pluto can be updated to allow the named functionality.
Cleanest I think would be for the 'render-config/page/portlet' complexType to also contain
a preferences element that can provide additional data to that specific portlet instance,
but this might very well be a lot of work internally.
                
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message