Hello David, If you define a <Context ...> for a particular app where the path matches the name of the .war file, the .war will not be unpacked by Tomcat under any circumstances. I imagine you have something like this in server.xml or in a context configuration file:
<Context docBase="myapp" path="/myapp" /> in this case a .war file named "myapp.war" will *not* be unpacked. You have to do it yourself or change the docBase to point to the .war file directory such as: <Context docBase="myapp.war" path="/myapp" /> In this case, Tomcat still won't unpack the .war file, but that doesn't matter because it is serving the app from the unpacked .war file. Jake Tuesday, November 26, 2002, 9:16:10 AM, you wrote: DB> Andoni writes: >> When I put a .war file over to my tomcat server it doesn't work. >> - It only creates an empty directory in webapps. >> >> If I put over the war and unzip the file, it works fine. >> >> If I put over the .war file and set unpackWARs="false" it does not work. >> - The unpack command is understood though as it does not create the >> directory in webapps >> >> I am using Tomcat 4.0.4. Has anyone come across anything similar? >> >> Thanks in advance, >> >> Andoni. >> >> >> -- >> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> >> DB> Hello Andoni, have u tried to build and deploy using ant? david. DB> -- DB> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> DB> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- Best regards, Jacob mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
