> From: behofmann [mailto:behofm...@gmail.com] > Subject: Serving Multiple Application Versions within the same Context > > While designing this application, I would like the ability to serve > multiple application versions within the same context.
Do you really want to do that? Wouldn't it be better to have a separate <Context> for each version? Mixing them together in the same classloader (one per <Context>) sounds really risky as well as being a maintenance nightmare. It would be better to deploy each application version as a separate <Context>. If you want to use the version numbering scheme you mentioned as an example, simply name the webapp .war files (or directories) as follows: webapps/production#1.0.war webapps/production#1.1.war Yes, that really is a # sign in the file name (omit the .war if using directories). > allowing me to direct Company A to > www.mycompany.com/production/1.0/index.jsp and > Company B to www.mycompany.com/production/1.1/index.jsp? You could have a webapp named just production that consists of nothing but a filter that forwards the request to the appropriate version based on the origin of the request. The standard URL rewrite filter should be able to do that for you: http://tuckey.org/urlrewrite/ - 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 unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
