I've created a context for my webapp in server.xml so that I could set up a connection pool.
In doing so, Tomcat raises an exception on startup while trying to unpack the war, saying that the directory (into which it is trying to unpack) does not exist or is unreadable. If I create an empty directory there, it does start up, but of course, does not unpack.
Here's the top of the exception stack trace:
Here's root elem of the context from server.xml:
If I change the docbase to name the war (docBase="foobar.war"), the app runs, but does not unpack into a dir - this is not what I want.
It seems to be a catch-22. It won't start w/o an existing target directory to unpack into, and it won't unpack if the directory exists.
Obviously I've misunderstood something in the context declaration, but I'm stumped for the moment.
In doing so, Tomcat raises an exception on startup while trying to unpack the war, saying that the directory (into which it is trying to unpack) does not exist or is unreadable. If I create an empty directory there, it does start up, but of course, does not unpack.
Here's the top of the exception stack trace:
Here's root elem of the context from server.xml:
If I change the docbase to name the war (docBase="foobar.war"), the app runs, but does not unpack into a dir - this is not what I want.
It seems to be a catch-22. It won't start w/o an existing target directory to unpack into, and it won't unpack if the directory exists.
Obviously I've misunderstood something in the context declaration, but I'm stumped for the moment.