|
Home > Archive > WebSphere Portal Server > October 2005 > PortletData, concrete portlet instance, and JSR 168
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
PortletData, concrete portlet instance, and JSR 168
|
|
|
| I have a portal page that contains two instances of my portlet. These instances have different settings, but the settings for each instance are shared by all users (in a group).
With the IBM portlet API, this is done using PorletData. As it says in the WPS documentation:
"There can be many PortletData objects parameterizing the same concrete portlet. Each PortletData object along with the concrete portlet comprises a concrete portlet instance."
and
"If an administrator puts a concrete portlet on a group page, then the PortletData object contains data stored for the group of users. This holds true for a group of users who have view access to the page."
Now I need to move this portlet to the JSR 168 API. So I am using PortletPreferences rather than PortletData. Making the preferences read-only achieves sharing the values among all users. However, the value of a read-only PortletPreference is also bein
g shared by all instances of the portlet. If I change the value of a preference in one portlet instance (using configuration mode), WPS applies the change to all portlet instances.
Is there any way to get the behavior that I had with PortletData (values stored per concrete portlet instance) using the JSR 168 API?
Thanks,
Dennis
| |
|
| IBM has told us the only way to do this without inventing your own PortletData equivalent for JSR 168 is to make a copy of the portlet for each unique placement you need. You can do this in the portal admin via Portlet Administration -> Portlets, and then
one of the icons to the right of all portlets is "Copy portlet" (note you still only need one WAR). This is only really viable if you have just a handful of placements, I think.
|
|
|
|
|