> -----Original Message----- > From: Mark Thomas [mailto:ma...@apache.org] > Sent: Monday, January 13, 2014 3:16 PM > To: Tomcat Users List > Subject: Re: META-INF/Context.xml path question > > On 13/01/2014 17:38, Bob DeRemer wrote: > > We're trying to determine if it's possible to build a WAR with an > > embedded META-INF/Context.xml > > It is context.xml, not Context.xml. Case matters. > > > that defines the webapp path to be > > different then the WAR file name. > > No, it is not possible to do this. > > > Let's say we have > > AppServer-<version>.war, but we want to access it as: > > http://<host>/Server. In addition, we want to support > > uploading/installing the WAR both from the Manager app as well as > > using ftp/command-line to copy the WAR and restart Tomcat. This way, > > it's pretty much automatic without editing/creating additional XML > > files. > > > > If this works, then we can have identifiable WAR files, but with a > > common/standard webapp path. > > The way to have identifiable WARs is to use the version element of the > filename. For example, server##1.0.15.war will be auto-deployed with a > context path of /server. The version tag can be pretty much anything you like > as > long as the file name is valid. You don't have to be using parallel > deployment to > make use of it.
version syntax works great, thx > > > We have reviewed the docs and the only approach that has worked for us > > is adding a separate Context element to the <Tomcat>/conf/Server.xml > > file. > > It is server.xml. Again, case matters. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
