Re: Controlling context name of exploded WAR file (?)

----- Original Message -----
From: "John Crossman" <John.Crossman@xxx.com>
To: <resin-interest@xxx.com>
Sent: Thursday, April 04, 2002 12:40 PM
Subject: RE: Controlling context name of exploded WAR file (?)

>
> Would it work to use a wildcard in the app-dir attribute value (as below)
so that CoolApp_1.35.war and CoolApp_1.36.war would expand to CoolApp
without having to restart the server?
>
> <web-app id="CoolApp" app-dir="CoolApp_*" />
>
> ??

I doubt it. How would the container implement the transition, when you
upgraded the server? What would happen to users interacting with
CoolApp_1.35 when you suddenly switched to CoolApp_1.36?

--
Martin Cooper
>
>
> -----Original Message-----
> From: Martin Cooper [mailto:martin.cooper@xxx.com]
> Sent: Wednesday, April 03, 2002 9:52 PM
> To: resin-interest@xxx.com
> Subject: Re: Controlling context name of exploded WAR file (?)
>
>
> Add this to your resin.conf:
>
> <web-app id="CoolApp" app-dir="CoolApp_1.35.war" />
>
> --
> Martin Cooper
>
>
> ----- Original Message -----
> From: "John Crossman" <John.Crossman@xxx.com>
> To: <resin-interest@xxx.com>
> Sent: Wednesday, April 03, 2002 3:58 PM
> Subject: Controlling context name of exploded WAR file (?)
>
>
> > If I have a WAR file named  CoolApp_1.35.war  How can I instruct Resin
> > to explode this file into a directory (and thus a context) named
> > "CoolApp" instead of "CoolApp_1.35" ?
> >
> > John
> >