To get Tomcat to recognize the new deploy, the previous deploy has to not exist! It only recognizes a new war on its "first deploy". So you have to delete the previous files.
Manually, in webapps, first delete the war, then the respective exploded dir hierarchy, and finally the respective dir in the work dir hierarchy. Then drop in the war in webapps (it's been awhile since I did a manual deploy, so I am pretty sure that is what it took to get it going). The key thing is clearing the existing one all out so Tomcat will deploy the new one - if anything is there in that context, then it will not. With Ant, use the Tomcat "deploy" and "undeploy" tasks. If previously deployed by dropping the war in webapps, then manually delete as above before the first use of "deploy" or there will be problems. The Tomcat Ant tasks are by far the easiest method I have found. The 3 app servers I have used (WebSphere, WebLogic, and Tomcat) all do it differently, behave differently, and have different side effects (or features ;-). > -----Original Message----- > From: Dan Allen [mailto:[EMAIL PROTECTED] > Sent: Saturday, March 29, 2003 11:33 PM > To: [EMAIL PROTECTED] > Subject: it's always the simplest things (redeploy) > > > I can't for the life of me understand why this has to be so > difficult. It seems a major flaw of tomcat not to be able to simply > redeploy and activate an application from a war file. I have read many > posts on the subject from the archives of this list and no one seems > to have a definitive solution. The solution just seems to be "just > use resin for development, it actually works right, then just deploy > on tomcat." Since I have invested a great deal of time in tomcat, I > wish not to give up this easily. > > In short, what does it take to drop a war into the webapps > directory, overwriting a previous war and get tomcat to recognize > the timestamp is newer and reissue the files so that you can see the > changes when you visit the application in the browser? I am tempted > just to do my development directly inside the web container to avoid > this issue all together, but that just doesn't seem to be the right > way to go about things. > > Since this question comes up so often, maybe we can work out a full > answer in this thread so that it doesn't have to be asked again. > > Dan > > -- > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Daniel Allen, <[EMAIL PROTECTED]> > http://www.mojavelinux.com/ > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Microsoft's Law of Software Engineering: > Don't worry if it doesn't work right. > If everything did, we'd be out of a job. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
