: The problem is that each time they grab updated code (a new WAR file) they
: overwrite their context.xml file with the default settings.
:
: Is there some more user-friendly way to deal with this configuration issue?
: How do others that provide downloadable WAR files do this?
This is the opposite of what I've seen: usually, the context.xml (the
version copied to {tomcat}/conf/{engine}/{host}/{context-name}.xml) is
*not* overritten with the (newer) version in the newly-deployed WAR
file.
as for dealing with this issue:
As context.xml is Tomcat-specific, you could expect a certain level
of Tomcat expertise from your users. By "expertise" in this case, I
mean, "remove the old context XML file before deploying the new WAR, to
make sure the newer file is copied over."
-QM
--
software -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
