Renaming "everything" is a very simple operation. If the webapp is
constructed correctly it should operate regardless of context path and
make adjustments as necessary. At most, some links between webapps will
have to be updated to reflect the adjustments in path.
I also can't recommend Apache httpd in front unless the site is a mixed
bag of technology -- perl, php, java, user client based html authoring,
etc., ...
All I can say is I have a different opinion on this point.
--David
Gregor Schneider wrote:
Hi David,
assuming the client gets his software delivered from different
vendors, one
day changes his mind to make another app his default application, then
what?
rename everything over again?
The best solution is, leave the web-app it's name and forward with a
index.jsp inside the ROOT-context to the required app since changing this
file is way easier than renaming the wep-apps.
Besides, if it's a real-world-app, I suggest having Apache HTTP in
front so
that you can also use all those feature Tomcat lags, like url-rwriting
etc.
Just my 0.02 €
Gregor
--
David Smith
Network Operations Supervisor
Department of Entomology
Cornell University
2132 Comstock Hall
Ithaca, NY 14853
Phone: (607) 255-9571
Fax: (607) 255-0940
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
