21 June 01
How about this: Use a production server inhouse with Tomcat installed and a
separate deployment box which serves to the world.
Utilize CVS and everyone working checks in or merges their changes and
deploy to the Production Tomcat server and restart four times a day. The
times can be well published, so everyone knows when the next update must be
checked in.
Joe Dalessandro
---------------
e: [EMAIL PROTECTED]
-----Original Message-----
From: Robert De Niro [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 21, 2001 10:20 AM
To: [EMAIL PROTECTED]
Subject: tomcat, and servlet testing in a multi-user environment
Hi!
We are several programmers who are programming servlets and jsp on our
tomcat server, and each time we modify a servlet or a jsp, we have to
restart tomcat so it takes in consideration our changes, and our problem is
that we are working everyone from his computer at the same time, so when
someone has made some changes and he wants to restart tomcat, it annoys the
others who may be testing their servlet.
So is there a way to make tomcat aware of new changes without restarting it
or should we install a tomcat on everyone's machine ?
Thanks!
--
_______________________________________________
FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup
Make PC-to-Phone calls with Net2Phone.
Sign-up today at: http://www.net2phone.com/cgi-bin/link.cgi?121
