Hi Rickard,
> Hi!
>
> > Ok, this is the Window hack but anyway I was thinking about that issue
> > too, especially on server crashes (will never happen ;-) it would be
> > fine to be able to recover the state of deployment (as I had this in an
> > earlier version). But how would that behave in conjunction with the
> > Autodeployer? J2eeDeployer starts, recoveres all deployments,
> > Autodeployer starts, redeploys all apps that are still available in the
> > observed directories.
>
> 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
\Daniel
>
> If we change the J2EEDeployer to resume deployments on startup that would be
> a great feature I think.
>
> /Rickard
