Yes, all 6 should be added to be consistent. If the tomcat deployer is going to handle the notification at the end of a deploy which is associated with a redeploy, why can't it it do the initial notification at the start of undeploy by looking to the DeploymentInfo.isRedeploy flag?

Jean-frederic Clere wrote:


That means we would need:
BEGIN_DEPLOY/END_DEPLOY
BEGIN_REDEPLOY/END_REDEPLOY
BEGIN_UNDEPLOY/END_UNDEPLOY
to be able to know the result of the action, wouldn't we?

In fact to prevent the 404 I just need to forward the BEGIN_REDEPLOY to
Apache httpd. (Tomcat has its event to tell that a Context is up again).

Cheers

Jean-Frederic

 Most likely a begin/end notification is the cleanest way to introduce
the notifications.
   /** The JMX notification type sent when a undeploy i

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

_______________________________________________
jboss-development mailing list
jboss-development@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development


_______________________________________________
jboss-development mailing list
jboss-development@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development