portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shinsuke SUGAYA (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Resolved: (JS2-644) Remote Portlet Application Deployer
Date Tue, 23 Jan 2007 13:56:49 GMT

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

Shinsuke SUGAYA resolved JS2-644.
---------------------------------

    Resolution: Fixed

Done. (revision 499006)


> Remote Portlet Application Deployer
> -----------------------------------
>
>                 Key: JS2-644
>                 URL: https://issues.apache.org/jira/browse/JS2-644
>             Project: Jetspeed 2
>          Issue Type: New Feature
>          Components: Deployment
>    Affects Versions: 2.1
>            Reporter: Shinsuke SUGAYA
>         Assigned To: Shinsuke SUGAYA
>             Fix For: 2.1
>
>
> Overview
> --------
> Remote Portlet Application Deployer(RPAD) deploys a portlet from remote
> portlet repositories into a Portal server, such as Jetspeed2, directly. RPAD
> consists of 2 parts: RPAD API and RPAD Portlet. RPAD API defines the
> programing interface to access to remote portlet repositories. RPAD Portlet
> provides JSR 168 compliant portlet to deploy a target portlet from remote
> repositories.
> +---------------------------+
> |   Portal Server(J2,...)   |
> +---------------------------+
> |       RPAD Portlet        |
> +---------------------------+
> |         RPAD API          |
> +---------------------------+
>              A Download
>              V Access
> +---------------------------+
> | Remote Portlet Repository |
> +---------------------------+
> | Portlet | Portlet | ...   |
> +---------------------------+
> Design
> ------
>         +-----------------------------------+
>         |           RPAD Portlet            |
>         | (RPADPortletFilter + JSF Portlet) |
>         +-----------------------------------+
>                        V Call RPAD API
> +---------------------------------------------------+
> |                RepositoryManager                  |
> +---------------------------------------------------+
>          V                      V                V
> +------------------+ +----------------------+ +-----+
> | SimpleRepository | | WebServiceRepository | | ... |
> +------------------+ |        (TBD)         | +-----+
>                      +----------------------+ 
> Class Description
> -----------------
>  RPAD API:
>   Class org.apache.jetspeed.portlets.rpad.RepositoryManager
>    RepositoryManager manages Repository instances. Portal, such as Jetspeed2,
>    calls methods of this class to access remote portlet repositories.
>   Interface org.apache.jetspeed.portlets.rpad.Repository
>    RPAD supports a variety of kinds of portlet repositories. A portlet
>    repository needs to implement this interface. Repository manages
>    PortletApplication instances for a remote portlet repository.
>    Portal can access portlet information in a remote portlet repository via
>    this class.
>   Class org.apache.jetspeed.portlets.rpad.PortletApplication
>    This class has properties of a portlet application, such as a portlet name,
>    url to download war file.
>   Class org.apache.jetspeed.portlets.rpad.simple.SimpleRepository
>    SimpleRepository is a file-based repository. If a portlet provider puts
>    a repository site descriptor for a remote portlet repository, using
>    SimpleRepository, the provider delivers portlets to a Portal server.
>    The syntax of the repository site descriptor is under discussion with
>    PRP(https://prp.dev.java.net/). We will define it by the first week of 
>    Feb.
>  RPAD Portlet:
>   The current implementation is JSF-based portlet.
>   Class org.apache.jetspeed.portlets.rpad.portlet.RPADPortletFilter
>    RPADPortletFilter initializes RepositoryManager instance. 
>   Interface org.apache.jetspeed.portlets.rpad.portlet.deployer.PortletDeployer
>    RPAD Portlet calls PortletDeployer#deploy(PortletApplication) to deploy
>    the target portlet into your Portal. If you implements PortletDeployer
>    class for your Portal, RPAD works on your Portal.
>   Class
>    org.apache.jetspeed.portlets.rpad.portlet.deployer.impl.JetspeedPortletDeployer
>     This class is PortletDeployer implementation for Jetspeed2.
> TODO IN THE FUTURE
> ------------------
>  - Manage a portlet version in J2
>  - Store portlet information to DB, not memory
>  - Move RPAD to under Apache Portals sub-project for other portals to use RPAD

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