The notification type should be added to the existing MainDeployerConstants

org.jboss.deployment.MainDeployerConstants
{
   /** The JMX notification type sent when a deployer is added */
   public static final String ADD_DEPLOYER = "org.jboss.deployment.MainDeployer.addDeployer";
   /** The JMX notification type sent when a deployer is removed */
   public static final String REMOVE_DEPLOYER = "org.jboss.deployment.MainDeployer.removeDeployer";
   /** The JMX notification type sent when a deploy is performed */
   public static final String DEPLOY = "org.jboss.deployment.MainDeployer.deploy";
   /** The JMX notification type sent when a undeploy is performed */
   public static final String UNDEPLOY = "org.jboss.deployment.MainDeployer.undeploy";
   /** The JMX notification type sent when a undeploy/deploy cycle is performed */
   public static final String REDEPLOY = "org.jboss.deployment.MainDeployer.redeploy";
}

One question is whether there should be BEGIN_DEPLOY/END_DEPLOY notifications that would allow one to determine the outcome of the deploy. Most likely a begin/end notification is the cleanest way to introduce the notifications.

Jean-frederic Clere wrote:

On Fri, 2006-09-22 at 08:37 -0700, Scott M Stark wrote:

You can pass in a hint as a url parameter "file:/.../deploy/my.war?
redeploy=true" so that the main deployer can set a flag in the
deployment.


Ok, this seems to work. Now I have the information that the undeploy()
occurs in MainDeployer because of a redeployment.

To send the information to my listener (and later to Apache httpd) I am
thinking of using a Notification("StartReDeploy", ...) and use the
DeploymentInfo to have the Host and the Context information.

Any comments?

Cheers

Jean-Frederic