> -----Original Message----- > From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] > Sent: Friday, February 17, 2012 9:22 AM > To: Tomcat Users List > Subject: RE: generic deployment question > > > From: Jeffrey Janner [mailto:jeffrey.jan...@polydyne.com] > > Subject: RE: generic deployment question > > > But, really, I just wanted to know if my original suggestion > > would cause issues with Tomcat. > > As Pid stated, it might work, but it's not a guaranteed deployment > mechanism. > > > Essentially, I don't see why I should zip up an app directory > > structure into a war file, just so Tomcat can unzip it a couple > > of dozen times. > > No need to zip anything up, just make a copy of the directory for each > client. > > - Chuck
That's actually the current deployment mechanism that I'm wanting to get changed. Unfortunately right now, there are some application related config files buried under the WEB-INF directory that have to updated for each customer, so I have to use the exploded directory structure anyway. Trying to get that changed so the information is retrieved from the database and then the database config info is done the "tomcat normal" way. Same with the location of the log4j properties file. Then there's only one or two other minor per/customer mods that I sometimes do that can be handled differently as well. I'm trying to limit the number of places I have to make updates on a deployment. __________________________________________________________________________ Confidentiality Notice: This Transmission (including any attachments) may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this transmission in error, please immediately reply to the sender or telephone (512) 343-9100 and delete this transmission from your system.
