On 08/08/2011 13:11, jenskreidler wrote:
>
> First of all thanks for the rapid answers and your time!
> I think I did not describe the scenario correctly, so I do this now:
>
> Assume you have a tomcat 'multiple-instances' setup like this
> /srv/tomcat/instance-1/
> /srv/tomcat/instance-2/
> ...
-
regardless of its filename - is mounted at the instance's root context?
jenskreidler
--
View this message in context:
http://old.nabble.com/Deploying-ROOT-Context-for-variable-.war-filename-tp32216447p32217790.html
Sent from th
On 08/08/2011 10:30, jenskreidler wrote:
>
>
> Pid * wrote:
>>
>> On 08/08/2011 09:56, jenskreidler wrote:
>>>
>>> Hi tomcat-users,
>>>
>>> using tomcat 7, is it possible to mount the ROOT context path for a .war
>>> file, where the .war file will have a variable file name, i.e. building a
>>> .w
ns that the war file is somewhat fixed to the
pattern "ROOT##[0-9].war, i'd be better that in tomcat the root context
could be configured using a directory, wherein the war file(s) reside, like
docBase="". but I've noticed that using that (in a context.xml or in
ROOT.xml) yo
On 08/08/2011 09:56, jenskreidler wrote:
>
> Hi tomcat-users,
>
> using tomcat 7, is it possible to mount the ROOT context path for a .war
> file, where the .war file will have a variable file name, i.e. building a
> .war by a continuous integration server.
> For example, you get a myapp-3.2.0-20
-build255.war and so on.
I'd like to convene with this ci-build ordering, the war file naming scheme
and to automatic deploy the newest .war every night at the tomcat's ROOT
context.
Thanks in advance,
jenskreidler
--
View this message in context:
http://old.nabble.com/Deploying-ROOT-C
