RE: WAR file and context.xml overwriting on deployment
Hi, You could use a different, your own, configuration file. You would then have some logic into the file name, e.g. myconfigfile-v1 for WAR v1, and then when your ship WAR v2, use myconfigfile-v2, so it wouldn't overwrite the first, etc. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Joe Reger, Jr. [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 16, 2004 5:28 PM To: [EMAIL PROTECTED] Subject: WAR file and context.xml overwriting on deployment Hi. I have a java web app that I package as a WAR file. People download it. They install it on their instance of Tomcat. They configure application settings as variables in context.xml. 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? I understand that this may not be the traditional usage of WAR files and Tomcat. Ideas welcome. Thanks, Joe Reger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WAR file and context.xml overwriting on deployment
Hi. I have a java web app that I package as a WAR file. People download it. They install it on their instance of Tomcat. They configure application settings as variables in context.xml. 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? I understand that this may not be the traditional usage of WAR files and Tomcat. Ideas welcome. Thanks, Joe Reger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: WAR file and context.xml overwriting on deployment
: 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]
