2010/1/28 LI Daobing :
> my system: Ubuntu 9.04, x86_64, tomcat 6.0.18,
See the Changelog file for a list of issues fixed since 6.0.18. (Or
search the Bugzilla) I remember that something similar was there.
Best regards,
Konstantin Kolinko
-
Hello,
I am talking about the first one, and i am still digging on this problem, it
sounds that if autoDeploy is on and deploy a new war package will trigger
this problem. Maybe an undeploy is triggered during this process, which
remove the ROOT.xml in the conf/C*/l* dir
Thanks
在 2010-1-28 下午11:
On 1/28/10 9:46 AM, LI Daobing wrote:
> Hello,
>
> in http://tomcat.apache.org/tomcat-6.0-doc/config/context.html, there
> is a statement:
>
> "Once this file exists, it will not be replaced if a new WAR with a
> newer /META-INF/context.xml is placed in the host's appBase."
>
> but, in my practice,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daobing,
On 1/28/2010 9:46 AM, LI Daobing wrote:
> in http://tomcat.apache.org/tomcat-6.0-doc/config/context.html, there
> is a statement:
>
> "Once this file exists, it will not be replaced if a new WAR with a
> newer /META-INF/context.xml is placed
Hello,
in http://tomcat.apache.org/tomcat-6.0-doc/config/context.html, there
is a statement:
"Once this file exists, it will not be replaced if a new WAR with a
newer /META-INF/context.xml is placed in the host's appBase."
but, in my practice, this file is always be replaced, I need help on
this
