Redeploy is not used during a hot-redeploy. The URLDeploymentScanner
simply does an undeploy/deploy the same as the redeploy in main. Both
the scanner and main deployer need to be marking a deployment as in the
process of being redeployed. This should be propagated via the
DeploymentInfo and WebApplication.
Sacha Labourey wrote:
That is what I mean: the MainDeployer could "share" this
that it is a redeploy with any other piece of code, including the
tomcatdeployer, by setting a temporary thread local variable that
could be checked by any deployer.
Jean-frederic Clere wrote:
> On Thu, 2006-09-21 at 09:36 +0200, Sacha Labourey wrote:
>> What about having the MainDeployer set a thread context variable
>> indicating whether we are inside a "Redeploy" scenario?
> MainDeployer knows that it is doing a redeploy(), the problem is just
> that the redeploy() should also be in the TomcatDeployer or that
> MainDeployer should tell to the TomcatDeployer that the undeploy() is
> called for a redeploy() (like undeploy(false) for a redeployement and
> undeploy(true) for an undeployement).