Rashmi Rubdi wrote:
I normally pre-compile the JSPs in the development environment,
package *only the class files* [Excluding the JSPs and the JSP Java files
generated by Jasper] into a WAR and then upload the WAR to production.
As James originally mentioned, I think if I ran HttpUnit directlly once on
production , it would generate the class files
the first time using the container that's installed on the Production
environment, thus by running HttpUnit or something similar (Apache Cactus)
accorss each environment (dev, staging, QA, prod) , the Ant build file would be
independent of the Web Container used on each environment
(if a different web container was used on each environment).
But, the above would require that the JSP files be uploaded to each environment.
yes. Which means you need the JDK there.
And, also if I were to run HttpUnit on a production environment, it would have
to be done during off-peak hours when not many visitors are on the site.
if you are live upgrading the site you will need a way to take a
specific node in the cluster offline, no? Or do you really do a full hot
deploy on your running system?
The way I've done upgrades is
-configure the router to not route to the system you are updating
-update that system by stopping the app server, installing the new
WAR/EAR and restarting
-test it is happy
-switch to it *only*
-upgrade the other other one
As long as you dont have a shared session state across machines, using
serialized java objects, this mostly works. doing a cold server restart
stops you getting burned by the local session state haiving legacy
serializations of the old classes.
And yes, you can automate all of this. commercial Routers have an SSH
console, so if you can automate SSH command you can manipulate the
router during deployment. I guess if you used consumer-grade
linksys/netgear boxes you could just deploy a UPNP component with your
webapp and have it automatically point the router at it.
-steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
