Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2005-09-28 13:14:46 →
Size: 1261
Editor: ZhongZheng
Comment: Added idea of implementing the deployments services as ws. Reformatted page.
← Revision 5 as of 2009-09-20 23:46:39 → ⇥
Size: 1262
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
[[TableOfContents(5)]] <<TableOfContents(5)>>
Line 23: Line 23:
   * [http://portals.apache.org/bridges  Portals-bridges] has been suggested
 1. Utilize a simple controller portlet[[BR]]		    * [[http://portals.apache.org/bridges|Portals-bridges]] has been suggested
 1. Utilize a simple controller portlet<<BR>>

Pluto 1.1 Admin Interface Discussions

Contents

  1. Pluto 1.1 Admin Interface Discussions
    1. Current requirements
    2. Current implementation ideas

Current requirements

  1. Command-line(maven) and admin portlet deployment should use the same deployment services (Implement the deployment services as ws).
  2. The admin portlets should work in Tomcat and other servlet containers that Pluto is deployed to.
  3. Deployment and undeployment of portlets will be supported by the admin portlets.
    • Hot deployment / undeployment should also be supported.
  4. Portal page layout will be supported by the admin portlet application.
    • We should also support the layout of portlets in different portlet applications on a portal page.
    • Changes to layout in a portal page should not require a restart of the Pluto portal.
  5. The admin interface will contain a portlet to support the editing of User Information Attributes (PLT 17).

Current implementation ideas

  1. Roll our own portlet framework
    • Not popular, due to concern about supporting it
  2. Use another portlet framework

  3. Utilize a simple controller portlet

    • Command design-pattern controller is a variation on this theme

Pluto/AdminPortlets (last edited 2009-09-20 23:46:39 by localhost)