Hi,
I'm running Tomcat 6.0.20 using JDK 6 update 14 on a 64 bits Debian
Lenny. I've unpacked a stock Tomcat 6.0.20 and deployed a web module to
the webapps directory. After I started and stopped the web module, I
noticed that the META-INF/context.xml had been copied to
conf/Catalina/localhost/[name of web module].xml.
I made a change to META-INF/context.xml and started Tomcat again, but
the copy in conf/Catalina/localhost/ appeared to be not updated. I
stopped Tomcat, removed the web module from webapps and started Tomcat
again. The copy in conf/Catalina/localhost still wasn't updated/deleted
and now Tomcat started complaining it couldn't find my webapp anymore.
I've been a long time Tomcat user and this has never ever been a problem
for me. I never noticed conf/Catalina/localhost contained a copy of my
context.xml files, but I could always modify context.xml and never
needed to explicitly delete the contents of conf/Catalina/localhost.
This is a rather scary situation. I'm not 100% sure why Tomcat does this
copying in the first place and I'm not at all sure what's going on with
the stale copies.
Anyone has any idea?
--
It's a cult. If you've coded for any length of time, you've run across someone
from this warped brotherhood. Their creed: if you can write complicated code,
you must be good.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
