Thanks for the replies. Your and Peter's reasoning make sense. Hot deploy feels very attractive for quick and easy bugfixes, but the risks of doing that in a production environment are fairly great. Sounds like I will be using a setup very similar to Peter's for production.
Thanks again, Brian O'Rourke On 10/31/05, Filip Hanik - Dev Lists <[EMAIL PROTECTED]> wrote: > > It is ready, but it is also very basic. like it only deploys .war files, > and as with any prod app, I would recommend not using hot deploy in > production anyway > > Filip > > Brian O'Rourke wrote: > > >Trying the dev list... > > > >---------- Forwarded message ---------- > >From: Brian O'Rourke <[EMAIL PROTECTED]> > >Date: Oct 26, 2005 1:37 PM > >Subject: FarmWarDeployer > >To: users@tomcat.apache.org > > > >Hello, > > > >Is FarmWarDeployer ready for use? I have played around with it a little > but > >have been unsuccessful so far. Is there any documentation of this that I > >have missed? I haven't been able to figure out how context configuration > is > >done for this deployer, but I noticed some oddities - e.g. that the > context > >name is determined by the name of the war file. Is there a working set of > >functionality that FarmWarDeployer handles now, or should I just stay > away > >from it altogether? > > > >Thanks, > >Brian O'Rourke > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
