Mailing-List: contact jetspeed-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jetspeed Developers List" <jetspeed-dev@portals.apache.org>
Message-ID: <2089621944.1240499730340.JavaMail.jira@brutus>
Date: Thu, 23 Apr 2009 08:15:30 -0700 (PDT)
From: "Jeroen Hoffman (JIRA)" <jetspeed-dev@portals.apache.org>
To: jetspeed-dev@portals.apache.org
Subject: [jira] Updated: (JS2-880) Full Wicket implementation of the admin
 portlets
In-Reply-To: <2089982809.1212504285220.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeroen Hoffman updated JS2-880:
-------------------------------

    Attachment: JS-880-removeAjaxExport.patch

Attached a patch removing Ajax export related files that are unused since wicketizing Import/Export and  the Portal Site Manager. See also my comment 10/Apr/09 07:35 AM.

> Full Wicket implementation of the admin portlets 
> -------------------------------------------------
>
>                 Key: JS2-880
>                 URL: https://issues.apache.org/jira/browse/JS2-880
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Admin Portlets
>    Affects Versions: 2.2.0
>            Reporter: Ate Douma
>            Assignee: David Sean Taylor
>             Fix For: 2.2.1
>
>         Attachments: JS-880-removeAjaxExport.patch, JS2-880-j2-admin-importexport.patch, JS2-880-jetspeed-importexport.patch, WicketPortletTrackingPortlet.diff, WicketProfilerAdmin.diff
>
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> We have a basic/example Wicket portlet implementation now for the User manager.
> But we need to expand/extend that portlet to provide the full functionalitiy needed, as well as support for the new security Preferences and attributes model implementation of JS2-869 and JS2-870.
> Furthermore, the other security and Site, Page, Profiler etc. portlet also should be rewritten using Wicket so we develop a common Wicket framework as standard for all admin portlets.
> Finally, the backed model used by Wicket should be abstracted such that a later replacement / further abstraction to use other backends like JCR or even flat XML storage is easy the incorporate.

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