On Wed, 21 Nov 2001, David Jencks wrote: > On 2001.11.21 14:06:58 -0500 danch wrote: > > > > > > Rickard Öberg wrote: > > > > > > > > That's much better, assuming I know where the tmp directory is. And I > > > don't, since the name keeps changing for each deployment. :-( > > > > > > Something people have been compaining about roughly forever. > > I think there are possible problems with trying to always use the same temp > dir -- for instance you might have problems removing the old copy before > you wanted to start the new one. We might be able to cook up some crazy > really hot redeploy whereby the new version is started before the old one > is stopped, allowing the requests in process in the old version to complete > while new requests go to the new version. > > What if we made the location of the temp dir visible through an mbean > representing the deployment? You could have a little ant task to ask where > the war went.
What I would really like, is to see that a redeploy needs to happen, and have the new file extracted into a new directory first, THEN have the old version undeployed, then have the new one deployed, then have the old one deleted. The current way things are done, there is a big window open while the undeployment and redeployment is happening. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
