Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of bob.deremer@thingworx.com
 designates 207.46.163.239 as permitted sender)
From: Bob DeRemer <bob.deremer@thingworx.com>
To: Tomcat Users List <users@tomcat.apache.org>
Subject: RE: META-INF/Context.xml path question
Thread-Topic: META-INF/Context.xml path question
Thread-Index: Ac8QhOt34N6mjfoKSYqEylrSH/uFugAF2SEAACfU0pA=
Date: Tue, 14 Jan 2014 15:17:17 +0000
Message-ID: 
 <864f1fff9fac4e4eb2c3dbfe18a10f54@BLUPR06MB193.namprd06.prod.outlook.com>
References: 
 <db64ac0c58864c7eadc05c981fec3b11@BLUPR06MB193.namprd06.prod.outlook.com>
 <52D44990.3090004@apache.org>
In-Reply-To: <52D44990.3090004@apache.org>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


> -----Original Message-----
> From: Mark Thomas [mailto:markt@apache.org]
> Sent: Monday, January 13, 2014 3:16 PM
> To: Tomcat Users List
> Subject: Re: META-INF/Context.xml path question
>=20
> 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
>=20
> It is context.xml, not Context.xml. Case matters.
>=20
> > that defines the webapp path to be
> > different then the WAR file name.
>=20
> No, it is not possible to do this.
>=20
> >   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.
>=20
> 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 deplo=
yment to
> make use of it.

version syntax works great, thx

>=20
> > 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.
>=20
> It is server.xml. Again, case matters.
>=20
> Mark
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org