> > What if AutoDeployer can ask J2EEDeployer if it is already deployed?
> >
> > I think this should be in the AutoDeployer somehow, but it's ok if it
has to
> > ask the J2EEDeployer for info about deployments.
>
> No. what happens then on regular redeploy... Or wait, do you mean:
>
> on AutoDeployer.startup he askes the J2eeDeployer.isDeployed () and only
> if not... and during his regular service the AutoDeployer dont asks
> anymore...
> This would need a flag in the AutoDeployers run method (boolean firstRun
> or startup) and a lot of work for the J2eeDeployer to not delete _all_
> in tmp/deploy
You need to separate which in /tmp/deploy is ok, and what should be removed.
Don't you have some persistent metainfo about the deployments? Maybe you
should keep a list of {URL,timestamp}. That way deploy() in J2EEDeployer
could easily check whether the URL being deployed is already deployed (i.e.
don't change AutoDeployer at all).
Yeah, this needs some thinking, testing, and tinkering. Go ahead ;-) This is
the fun part.
/Rickard
