geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@codehaus.org
Subject [jira] Commented: (GERONIMO-106) Deployment Planner base-class
Date Tue, 04 Nov 2003 15:12:06 GMT
The following comment has been added to this issue:

     Author: Gianny DAMOUR
    Created: Tue, 4 Nov 2003 9:10 AM
       Body:
Following the AbstractStateManageable commit, this patch was no more valid.

I will submit an updated patch fixing this. This patch also adds the following features:

DeploymentContext defines now the following JMX operations:

    public void startDeployment() throws DeploymentException;
    public void stopDeployment() throws DeploymentException;
    public void undeployDeployment() throws DeploymentException;
    public void redeployDeployment() throws DeploymentException;

These operations trigger the expected deployment action on a deployment unit. More accurately,
it triggers the planning of a deployment context goal (package org.apache.geronimo.deployment.goal)
and the execution of the resulting plan set. The planning is performed by the deployment planner,
which has mounted this deployment context, and the execution is delegated to the DeploymentController.

A deployment repository has been added in order to track the deployments currently mounted.
By now, only the "registered" files of deployments are tracked. In the future (I need to clean
this part), deployment states will also be tracked. The goal of this repository is to simplify
the implementation of ApplicationDeployer.

As I said, the "registered" files are tracked. More accurately, a scanner checks these files
and upon modification executes a command. By now, two files are automatically created in order
to trigger either the redeployment or the undeployment of a deployment. For instance, when
an archive module – archive.jar in the example - is deployed, the following files are created,
if required:
archive.jar_REDEPLOY: if one "touch"es this file, then the deployment is redeployed; and
archive.jar_UNDEPLOY: if one "touch"es this file, then the deployment is undeployed.
---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=GERONIMO-106


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-106
    Summary: Deployment Planner base-class
       Type: Improvement

     Status: Assigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: Apache Geronimo
 Components: 
             deployment

   Assignee: Aaron Mulder
   Reporter: Gianny DAMOUR

    Created: Tue, 21 Oct 2003 9:55 AM
    Updated: Tue, 21 Oct 2003 10:00 AM

Description:
This patch is an enhancement of GERONIMO-102, which was a "sample code" used to progress a
discussion about the responsibities of Deployment Planners.

It should fix most of the drawbacks identified by Jan Bartel. Some points have not been fixed.
Indeed, some of them require a significant impact of the code-base.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message