> From: nyronian [mailto:[EMAIL PROTECTED]
> Subject: RE: deploy outside of appBase w/Manager
>
> I wanted to do my due diligence before coming up with
> my own deployment solution (like the scripting solution
> you recommended).
You could probably use the manager as is to
Charles R wrote:
>
>> From: nyronian [mailto:[EMAIL PROTECTED]
>> Subject: Re: deploy outside of appBase w/Manager
>>
>> First, the context.xml is simple:
>> > privileged="false" />
>
> As you have discovered, and we have discussed _many_ time
> From: nyronian [mailto:[EMAIL PROTECTED]
> Subject: Re: deploy outside of appBase w/Manager
>
> First, the context.xml is simple:
> privileged="false" />
As you have discovered, and we have discussed _many_ times on this
mailing list, the path and docBase attribu
Excuse me...I meant version 5.5.20
nyronian wrote:
>
> I am on 5.0.25.
>
> Here are the different deployments I have tried and the problems I have:
>
> First, the context.xml is simple:
>
> privileged="false" />
>
> The server.xml Host entry is:
> autoDeploy="false" deployOnStartup="
I am on 5.0.25.
Here are the different deployments I have tried and the problems I have:
First, the context.xml is simple:
The server.xml Host entry is:
(I have toyed with different settings on unpackWARS, autoDeploy and
deployOnStartup without success)
Scenario 1:
1. Place the contex
On Tue, 2007-10-02 at 16:51 -0400, nyronian wrote:
>
> To put it simply, I would like to use the manager to deploy an app
> just like
> auto-deployment works but I need to change the context (path) without
> changing the name of the war.
>
> I am trying to implement the following deployment requi
