> Any other ideas on why Tomcat doesn't like *this* particular .war file?
It gets weirder. If while Tomcat is running, I rename 'bendev.war' to
'abc.war', Tomcat immediately sees it, expands it and deploys the new
webapp.
(It was a nice experiment to prove that I have not hard coded the context
name anywhere in my app, because it all works fine under the 'abc' context
name. :)
This is on my desktop Win2000 machine, and I'm an administrator on it, so I
don't think I could be having file permission problems. (The file is
neither hidden nor read-only according to the properties.)
I did have a bendev.xml file in webapps (contents below) but I've tried it
without that with no change.
<Context path="/bendev" docBase="bendev" debug="4">
<Logger
className="org.apache.catalina.logger.FileLogger"
prefix="localhost_bendev_log."
suffix=".txt"
timestamp="true" />
</Context>
There's nothing in the global web.xml or server.xml that's specific to the
'bendev' context. (The only thing I've changed is the port number from 8081
to 80, anything else I do in a ${context}.xml file as above or in the
context-level web.xml file.
It can't not like the *name*, that's just nuts! (I just know this is going
to turn out to be something simple and really embarrassing...)
--
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University PA Information Resources Management
