I understand that there are caveats to using the manager application with contexts that have been specified within the server.xml file... I have 3 virtual hosts setup, all are separate web applications. Each has the manager context application associated to themselves. The manager appears to respond to listing the applications within each virtual host correctly, I have made the following folder structure: webapps\ webapps\vhost1\ webapps\vhost2\ and set the appbase for each virtual host to the correct folder. I then specify a context with a docbase of 'webapp1.war' for vhost1. If I restart the entire tomcat server, all looks normal, I get webapps\vhost1\webapp1.war webapps\vhost1\webapp1\ etc but when I stop the context under webapps1 via the webapps1 manager and start it again, it extracts the webapp1.war to the webapps folder instead of the appbase of webapps\vhost1 Essentially, we want to be able to upgrade virtualhosts without having to reload tomcat itself (affecting other web application on the same server). We also need the context pre-declared so we may take advantage of jdbc connection pooling..... -Art
