Return-Path: 
 <jetspeed-dev-return-29707-apmail-portals-jetspeed-dev-archive=portals.apache.org@portals.apache.org>
Delivered-To: apmail-portals-jetspeed-dev-archive@www.apache.org
Received: (qmail 21043 invoked from network); 3 Jul 2007 17:58:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 3 Jul 2007 17:58:29 -0000
Received: (qmail 84028 invoked by uid 500); 3 Jul 2007 17:58:30 -0000
Delivered-To: apmail-portals-jetspeed-dev-archive@portals.apache.org
Received: (qmail 84006 invoked by uid 500); 3 Jul 2007 17:58:30 -0000
Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:jetspeed-dev-help@portals.apache.org>
List-Unsubscribe: <mailto:jetspeed-dev-unsubscribe@portals.apache.org>
List-Post: <mailto:jetspeed-dev@portals.apache.org>
List-Id: <jetspeed-dev.portals.apache.org>
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Delivered-To: mailing list jetspeed-dev@portals.apache.org
Received: (qmail 83989 invoked by uid 99); 3 Jul 2007 17:58:30 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2007 10:58:30 -0700
X-ASF-Spam-Status: No, hits=-100.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Jul 2007 10:58:25 -0700
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id CF8BF7141F0
	for <jetspeed-dev@portals.apache.org>; Tue,  3 Jul 2007 10:58:04 -0700 (PDT)
Message-ID: <1184430.1183485484846.JavaMail.jira@brutus>
Date: Tue, 3 Jul 2007 10:58:04 -0700 (PDT)
From: "David Sean Taylor (JIRA)" <jetspeed-dev@portals.apache.org>
To: jetspeed-dev@portals.apache.org
Subject: [jira] Commented: (JS2-634) edit_defaults custom portlet mode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


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

David Sean Taylor commented on JS2-634:
---------------------------------------

Damn I let this one slip, simply forgot about it. The problem was it was not assigned to me.
We are planning to release 2.1.1 Friday July 6, I can't see how I can get this coded up that soon, not with all the other features and bug fixes I have promised others.

> 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
>            Reporter: Vitaly Baranovsky
>
> 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