I always do. The problem is, it undeploys the new war file, but it's not using it. It seems to have an old copy of the app stored somewhere else and is using that or context root is being switched to it. Why this is I don't know. But the behaviour is thus; any new files created by the app is created in the nnew undeployed application's directory but attempting to access it means it resolves the file path to the "ghost" app directory.
On 21 February 2011 22:16, Mark Thomas <ma...@apache.org> wrote: > On 21/02/2011 21:52, Lanre Abiwon wrote: > > I always load with Tomcat stopped. > > Then you need to delete the expanded ROOT directory as well as replace > ROOT.war. > > Mark > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > -- A Hundred Elephants can knock down the walls of a fortress. One diseased rat can kill everyone inside
