portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-634) edit_defaults custom portlet mode
Date Thu, 04 Oct 2007 07:20:50 GMT

     [ https://issues.apache.org/jira/browse/JS2-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Woonsan Ko resolved JS2-634.
----------------------------

       Resolution: Fixed
    Fix Version/s: 2.2

Finished for edit_defaults custom mode.
By the way, I will not try implementing the *migration* tool for some reason.
So, I'd like to mark this issue 'resolved' now.
Vitaly, if you still want a migration tool which might be contributed by someone, would you
create another issue for the tool? Thanks.

And, I wrote down some description below:

1. Basic functionality

Only users having admin rights (based on constraints/permissions) can use edit_defaults mode,
and
 the default preferences are to be stored in PSML pages.
To enable this feature, the portlet decoration properties should have
 'actions.factory=org.apache.jetspeed.decoration.CustomDecoratorActionsFactory'. See
 /decorations/portlet/tigris/decorator.properties.
Implemented edit_defaults and about custom portlet modes for the PickANumber portlet.

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 *autoSwitchingToEditDefaultsModes* to true for decorationValve in pipelines.xml like
the
 following:

     <property name="autoSwitchingToEditDefaultsModes"><value>true</value></property>

 b) Set the first constructor arg to true for portletFactory bean in registry.xml like the
 following:

    <bean id="portletFactory" class="org.apache.jetspeed.factory.JetspeedPortletFactory">
        <!--
        If the following argument is true, then this factory will create proxy instances for
 actual portlet instances. 
        Proxy instances will switch edit_defaults mode to edit mode automatically for portlets
not
 supporting edit_defaults mode.
        -->
        <constructor-arg index="0">
            <value>false</value>
        </constructor-arg>
    </bean>

 c) 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>

3. Limitations

 a) If the doEdit() method of a portlet is not public, then the system will not provide
 auto-dispatching for the portlet with no error.
 b) If a portlet provide edit_defaults mode, then the system will not provide auto-dispatching.
 Instead, it will hand over rendering to the portlet.
 c) If a portlet does not provide edit mode, then the system will not provide auto-dispatching.
 d) If a portlet application does not have custom mode mapping for edit_defaults, then the
system will not provide auto-dispatching.

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


Mime
View raw message