The scanner could use the MainDeployerMBean interface, or there could be
a DeployerExt extending Deployer, with the missing methods added.
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf
Of Jean-frederic Clere
Sent: Friday, September 22, 2006 6:02 PM
To:
JBoss.org development list
Subject: Re: [JBoss-dev] httpd and tomcatClustering gives 404
during redeploy.
On Fri, 2006-09-22 at 16:24 +0200, Sacha Labourey wrote:
> What you are looking for is for what happens at line 391-392 here:
>
http://fisheye.jboss.org/browse/JBoss/jboss-system/src/main/org/jboss/
> deployment/scanner/URLDeploymentScanner.java?r=1.1
The problem is the URLDeploymentScanner uses the interface
Deployer to reach MainDeployer.
It is not possible to add a redeploy method to Deployer
because that would break the interface (may be customer have
their own Deployer).
The undeploy method in Deployer is:
void undeploy(URL url) throws DeploymentException; The
information must be stored somewhere.
Any hints?
Cheers
Jean-Frederic
>
> Jean-frederic Clere wrote:
> > On Thu, 2006-09-21 at 07:27 -0700, Scott M Stark wrote:
> >
> >> Redeploy is not used during a hot-redeploy. The
> >> URLDeploymentScanner simply does an undeploy/deploy the
same as the redeploy in main.
> >>
> >
> > Well URLDeploymentScanner only passes the URL, how do I get the
> > information that it is a redeployement in MainDeployer?
> >
> > Cheers
> >
> > Jean-Frederic
> >
> >
> >> 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 knowledge
> >>> 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).
> >>>>
> >>>> Cheers
> >>>>
> >>>> Jean-Frederic
> >>>>
> >>>>
> >> _______________________________________________
> >> jboss-development mailing list
> >> jboss-development(a)lists.jboss.org
> >>
https://lists.jboss.org/mailman/listinfo/jboss-development
> >>
> >
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/jboss-development
> >
> >
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development