Hallo everybody,
At first I like to say that I always loved Tomcat and the job the
commiters/community does with it. But this change/version is just
frustrating...
I tried Tomcat 6.0.20 yesterday and was really disappointed about what
happend (since 6.0.18) with the handing of context.xml. The change was
on a minor (bugfixing) version, but it makes Tomcat backward
uncompatible for many people. The new behavior (coping context.xml to
/conf, redeploy on update of /conf/.../<ctxpath>.xml) just replaces the
old behavior, without a option the have the old one back.
1.
I have looked at the new documentation and the new code in
org.apache.catalina.startup.HostConfig.java. And my first question is:
what is reason behind redeploying the application after detecting an
update of /conf/.../<ctxpath>.xml? (6.0.18 restarts the application in
this case)
Just think about it: You have an tomcat production server with 200
applications. All application were deployed statically and they (and
you) have no .war files. You can't restart the tomcat. But you need to
update the database resource parameter in /conf/.../<ctxpath>.xml of an
application promtly. You edit the file, save it. In a minute a customer
calls you on the phone and tells the application is not accessible. You
look into appBase, but the app is not there. Tomcat has deleted it (in a
try to redeply, but there is not .war file to deploy) ?!?! Where are my
files?!?!?
2.
If I deliver a patch that makes the behavoir after updating a
/conf/.../<ctxpath>.xml configurable, could it be included in the next
version?
Something like <Context ...
onDetectContextXmlUpdate="redeploy|reload|ignore"> where "redeploy" is
default to keep new behavior
3.
If I deliver a patch that optionally turns off copying
/META-INF/context.xml to /conf/.../<ctxpath>.xml, could it be included
in the next version?
Something like <Host ... copyFirstApplicationContextXml="true|false">,
where "true" is default to keep new behavior
Thanks
Igor
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
