Has anyone seen anything like this:
I\'m using a script which basically undeploys an app using ant, puts the new war file in the deploy directory and then deploys it usi
work
and temp
directories?webapps
directory?conf/server.xml
file: <Host unpackWARs="..." autoDeploy="..."/>
War file is nothing but a zip file and it will get deployed once you start/ stop the server. Not sure about ant "Undeploy"
Kirubha
FWIW, we experienced something similar on a fresh, simple* WAR deployment on Tomcat 7.
I'm seeing compiled JSP classes appear as I visit the respective page. So the app works, it's just not exploded to the work area... not sure why.
I'm having a hard time explaining what has happened because this was an incremental application upgrade and the initial install required an identical process**, which went very smoothly. This suggests it isn't a tomcat configuration issue.
* We use deployment descriptor (xml) files so we can reuse the same war
** The process was to manually run a script that was packaged in the WEB-INF folder
[Update] I may have just answered my own question. If I'm reusing WAR files for different deployment contexts then perhaps a common exploded WAR is being used ?!