tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From AD <>
Subject root context path - war file not unwar'd
Date Mon, 19 Jan 2009 22:57:10 GMT

 I have an issue where inside a <host> i set the context path of "/" to a
directory inside webapps (myapp).  The issue is when i delete the directory
, on first startup the directory is not available yet (not unwar'd yet it
appears) so it auto-sets the root context path to the default tomcat
application.  If I simply restart tomcat, everything works as expected
(because the directory is now there).

Does anyone know if there is a way to ensure that new war files are unwar'd
prior to any other execution so this doesnt screw up the context path
settings?   We like to delete the directory when deploying new wars since we
have seen some issues not deleting the directories before.

Tomcat 5.5.26
Java 1.6
Solaris 10


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message