[
https://issues.apache.org/jira/browse/JS2-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542009
]
woon_san edited comment on JS2-634 at 11/12/07 5:17 PM:
----------------------------------------------------------
As a result latest work, the guide I wrote before should be modified. The
section 2 is simplified like the following:
2. (Optional) Automatic dispatching option
If a portlet does not support edit_defaults mode, but it supports edit mode,
then Jetspeed can
optionally provide automatic dispatching to doEdit() when the current portlet
mode is edit_defaults.
To enable this option:
a) Set the following property to true in /WEB-INF/conf/jetspeed.properties.
supported.portletmode.autoswitch.edit_defaults=true
b) Each portlet application should have custom portlet mode mapping
declaration like the following (in portlet.xml):
<custom-portlet-mode>
<description>a Custom Edit_defaults Mode</description>
<portlet-mode>edit_defaults</portlet-mode>
</custom-portlet-mode>
was (Author: woon_san):
As a result latest work, the guide I wrote before should be modified. The
section 2 is simplified like the following:
2. (Optional) Automatic dispatching option
If a portlet does not support edit_defaults mode, but it supports edit mode,
then Jetspeed can
optionally provide automatic dispatching to doEdit() when the current portlet
mode is edit_defaults.
To enable this option:
- Set the following property to true in /WEB-INF/conf/jetspeed.properties.
supported.portletmode.autoswitch.edit_defaults=true
> edit_defaults custom portlet mode
> ---------------------------------
>
> Key: JS2-634
> URL: https://issues.apache.org/jira/browse/JS2-634
> Project: Jetspeed 2
> Issue Type: New Feature
> Components: Customizer, PSML
> Affects Versions: 2.1.3
> Reporter: Vitaly Baranovsky
> Assignee: Woonsan Ko
> Fix For: 2.1.3, 2.2
>
>
> There is a wish for implementing "edit_defaults" custom portlet mode as
> descripted in JSR168 portlet specification:
> ----------------------------------------------------------
> PLT.A.3 Edit_defaults Portlet Mode
> The edit_defaults portlet mode signifies that the portlet should render a
> screen to set the default values for the modifiable preferences that are
> typically changed in the EDIT screen. Calling this mode requires that the
> user must have administrator rights. Therefore, only the portal can create
> links for changing the portlet mode into edit_defaults.
> Portlet developers should implement the edit_defaults portlet mode
> functionality by
> overriding the doDispatch method of the GenericPortlet class and checking for
> PortletMode("edit_defaults ").
> In the deployment descriptor the support for the edit_defaults portlet mode
> must be
> declared using
> <portlet-app>
> ...
> <portlet>
> ...
> <supports>
> ...
> <portlet-mode> edit_defaults </portlet-mode>
> </supports>
> ...
> </portlet>
> ...
> <custom-portlet-mode>
> <name> edit_defaults </name>
> </custom-portlet-mode>
> ...
> </portlet-app>
> -----------------------------------------------------------
> There is number of situations when there is need of different default
> preferences for same portlet type. There is a problem to change default
> preferences by administrator now. Because he must to edit psml files
> manually, without graphical interface.
> For example, i want my portal shows to all users rss feeds from bbc and cnn
> with RSS Portlets at main page of my portal. But administrators of my portal
> needs to know psml format to change read-only preferences, and they can't do
> it thru grafical interface.
> So, I think, many people wishes for edit_defaults portlet mode.
> So, this jira record is wish for edit_defaults portlet mode
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
