Theoretically, maybe, but in real-life heavy-duty production environments, I believe using Apache as a front to Tomcat has advantages, in areas as security, load-balancing, caching and scalability. Furthermore, the production architecture is not the issue here, as I've explained in my original post. The problem stems from the decision to separate the web-app and static-content to two projects in SVN, and this is due to the fact that different people maintain them.
Thanks anyway. Caldarale, Charles R wrote: > >> From: nlif [mailto:[EMAIL PROTECTED] >> Subject: How to serve two docBases under the same context path >> >> In production, I intend to use Apache to serve the static >> content, and Tomcat to process requests to the application > > Why are you wasting your time, energy, and resources to do that? Tomcat > is just as capable as httpd when it comes to handling static content. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY > MATERIAL and is thus for use only by the intended recipient. If you > received this in error, please contact the sender and delete the e-mail > and its attachments from all computers. > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/How-to-serve-two-docBases-under-the-same-context-path-tp20132698p20135565.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
