On 20/09/2011 09:53, Andy Chapman wrote: > I have a Tomcat 7.0.16 install with two WAR based webapps in it. > > First test case: > Two war files in <tomcat-home>/webapps at startup > 1. ROOT.war > 2. another.war > If I request http://localhost:8080/another/something it goes to the > another webapp. > > Second test case: > Two war files in <tomcat-home>/webapps at startup > 1. ROOT.war > 2. wibble.war > If I request http://localhost:8080/wibble/something it goes to the ROOT > webapp.
That isn't right. Looks like wibble.war failed to deploy. > Third test case: > One war file in <tomcat-home>/webapps at startup > 1. ROOT.war > Second war file added to <tomcat-home>/webapps after startup (with > auto-deploy on) > 2. another.war > If I request http://localhost:8080/another/something it goes to the ROOT > webapp. That isn't right. Looks like another.war failed to deploy. > It looks like Tomcat is adding the webapps contexts to it's "filter" > list in alphabetical order at startup and then adding any auto-deployed > WARs afterwards but I can't believe it is that simple. Can anyone > give/link to a proper explanation? Requests are mapped to contexts based on the longest matching context path (as per the Servlets spec). You can use the Manager app to see if apps have deployed and are started. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
