on 1/20. I turns out that the reason I was getting "Missing application web.xml" errors in my stdout.log
was because of a problem that arose during the undeployment precipitated by my deployment of a new
build. It appears (just based on Tomcat's behavior) that when you move a WAR file into the webapps directory, the first thing Tomcat tries to do is delete the old unpacked version. In my case, it failed to do that because (as I found) the servlet had open file handles to files inside the servlet's context directory. Windows XP doesn't let you delete files that it thinks are "in use", and I suspect that is the trouble Tomcat was running into. Anyway, it deleted everything except those files, including the web.xml file, which it then reported as missing.
When I modified my code to make sure the files were closed after being read, the problem went away. Well, I haven't had the fix in place long enough to be sure it has gone away, but at the very least it certainly seems to have helped a great deal, so I think the problem is solved.
--Paul Lynch (eph1v3t8 @ mailblocks.com)
---------------------------------------------- Mailblocks - A Better Way to Do Email http://about.mailblocks.com/info
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
