You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "David Sean Taylor (JIRA)" <je...@portals.apache.org> on 2008/03/27 20:09:24 UTC

[jira] Resolved: (JS2-860) Implement a second, Versioned Portlet Application Manager

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

David Sean Taylor resolved JS2-860.
-----------------------------------

    Resolution: Fixed

>  Implement a second, Versioned Portlet Application Manager 
> -----------------------------------------------------------
>
>                 Key: JS2-860
>                 URL: https://issues.apache.org/jira/browse/JS2-860
>             Project: Jetspeed 2
>          Issue Type: New Feature
>    Affects Versions: 2.2
>            Reporter: David Sean Taylor
>            Assignee: David Sean Taylor
>             Fix For: 2.2
>
>
>  Implement a second, Versioned Portlet Application Manager for clustered environments
> We are running into limitations with the NodeManager-based cluster support when deploying to clusters with replicated databases as well as replicated app servers.
> The default PAM (Portlet Application Manager) is not-appropriate for many deployments of the portal. I am implementing a second version of the PAM, with no listeners,
> and a simpler deployment algorithm based on a version number supplied in the jetspeed-portlet.xml metadata
> If this field is not found, or if it is equal to or less than the version in the database, then the PA will not be deployed.
> This will allow for dropping in 2..n PAs in a cluster, without re-registering. The problem with re-registering is that the registry algorithm deep deletes the old PA def from the database,
> create a new PA, with all new OIDs, invalidating all other PAs and portlets on other nodes in the cluster.

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