[jira] Commented: (JS2-634) edit_defaults custom portlet mode

["Woonsan Ko (JIRA)" <je...@portals.apache.org>]

    [ https://issues.apache.org/jira/browse/JS2-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567492#action_12567492 ] 

Woonsan Ko commented on JS2-634:
--------------------------------

Hi Vitaly, 

IMO, I think you should remove the line you added in the <supports> section of <portlet id="UserDetailsPortlet"> of portlet.xml:

    <portlet-mode>edit_defaults</portlet-mode>

The automatic dispatching option works only when the portlet does not support edit_defaults mode explicitly.
By the way, the portlet should support EDIT mode, so the system can do auto-dispatching.

To summarize:

 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>

 c) Your portlet must support EDIT mode and it must have public doEdit() method.
    (For example, if your portlet extends GenericServletPortlet, then it already has public doEdit() method.)


By the way, FYI, the PickANumber portlet is not an example for auto-dispatching option, but it is an example for manual implementation for edit_defaults mode.
If you set configurations properly, the bookmark portlet in the default-page.psml will work as an example of auto-dispatching option when you log in by admin after installation.

Regards,

Woonsan

> 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.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: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org