So, read-only preferences cannot be modified in "config" custom portlet
mode to be shared between users, doesn't it? So, does planned support of
"config" custom portlet mode in jetspeed-2? (Administrators can change
read-only preferences in "config" portlet mode. And this preferences are
shared between all users)
Part of JSR-168 spec:
PLT.A.2 Config Portlet Mode
The config portlet mode should be used by the portlet to display one or more
configuration views that let administrators configure portlet preferences
that are marked non-modifiable in the deployment descriptor. This requires
that the user must have administrator rights. Therefore, only the portal can
create links for changing the portletmode into config.
Portlet developers should implement the config portlet mode functionality by
overriding the doDispatch method of the GenericPortlet class and checking
for PortletMode("config").
The CONFIG mode of portlets operates typically on shared state that is
common to many portlets of the same portlet definition. When a portlet
modifies this shared state via the PortletPreferences, for all affected
portlet entities, in the doView method the PortletPreferences must give
access to the modified state.
In the deployment descriptor the support for the config portlet mode must be
declared using
<portlet-app>
...
<portlet>
...
<supports>
...
<portlet-mode>config</portlet-mode>
</supports>
...
</portlet>
...
<custom-portlet-mode>
<name>config</name>
</custom-portlet-mode>
...
</portlet-app>
2006/10/3, David Sean Taylor <[EMAIL PROTECTED]>:
Vitaly Baranovsky wrote:
> Ok, how about other part of my question? Can I change parameter for all
> users thru config portlet mode?
Once a user saves a preference, they will no longer look at the default
value. We don't have a feature to reset every single user's preferences
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
