----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
> Partitioning your execution environment for development purposes involves
> assigning a zone to each developer. Each zone is then configured with a
> single jserv instance, creating a partitioned execution environment.
> Assuming each jserv is configured with a developers individual class path
> ;-), this then provides a development environment where changes made by
one
> developer do not have an effect on other developers on a project.
Has anyone used this idea to stage releases also on a production
machine? What I am thinking about here is on a production server,
to partition releases of a site to allow an updated site to be completely
updated and tested on the production server as part of the final
release process. In other words, start with zone "release1" which say
is now the production code. As part of the final transition to release2,
have it running to do FINAL testing, then just replace the index.html
file at the root of the site, now pointing to release2.
Any thoughts from anyone out there? What I am trying to do is make
the transition between releases less hectic where we can do a day
or two of really FINAL testing on a production server while still
allowing the production site to run. Then switch the switch and be
sure that everything is there.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
