We had a similar problem on my last project. We ended up just using brute
force to solve the situation, we had
tomcat and apache serving from a specific directory. This directory would
actually be a symlink to the latest version of the code. We modified our Ant
build script to generate the war file (we were not using JBOSS) and name it
according to the date. This file was then moved to the proper environment
(QA, Staging, Production) and another script would unwar it into a directory
based on its name(we would unwar the file skipping jsps and code on the web
servers, and html, images, etc. on the app servers). The symlink would then
be updated to point at the latest code.
This is a major hack and lost most of the benefits of packaging the
application, but it was quick and easy, and did have the benefit that
rolling back to an older version of the application was as simple as
changing a symlink. This made debugging much easier.
Samuel
-----Original Message-----
From: Jim Crossley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 20, 2001 13:41
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Apache+Tomcat+JBoss
We're currently deploying our web apps (packaged as war files) on
Apache+Tomcat 3.2, and it works fine, except for one problem. We'd like
to be able to redeploy our apps independently of each other, without
having to stop and restart Tomcat.
Though we currently don't use EJB's in our apps, the JBoss J2EEDeployer
is enough of a reason for us to integrate JBoss into our environment.
Everything works great between JBoss and Tomcat, but I'm having a hard
time deciding how to integrate Apache.
I've searched the archives, and there seems to be no reasonable way to
split the serving of static and dynamic content between Apache and
Tomcat, respectively. The two solutions proposed are best summarized in
these two messages:
http://www.mail-archive.com/[email protected]/msg02681.html
http://www.mail-archive.com/[email protected]/msg01839.html
With all due respect -- I understand the complexity of the problem --
these solutions are unacceptable to us, the first because Tomcat is
still serving both static and dynamic content, and the second because it
defeats the purpose of the war file, making deployment even more
error-prone than it already is.
Is there a better way?
Thanks.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
