Re: Persistent Context names with auto-deploy

[Craig R. McClanahan]

On Thu, 11 Apr 2002, bryan collins wrote:

> Date: Thu, 11 Apr 2002 08:43:42 +1000 (EST)
> From: bryan collins <[EMAIL PROTECTED]>
> Reply-To: Tomcat Users List <[EMAIL PROTECTED]>
> To: Tomcat Users List <[EMAIL PROTECTED]>
> Subject: Re: Persistent Context names with auto-deploy
>
> I am using manager for the intial deployment of an app.
> I don't want to have to re-deploy the apps each time TC starts up.
>
> Is there a way for TC to remember what path you deployed an app on via
> the manager app?
> Keep in mind that unpackwars=true must be set for filesystem access.
>

This will ultimately be a feature of the HEAD branch (what will ultimately
become Tomcat 4.1).  Any apps deployed via Manager, or changes made using
the admin app, will cause server.xml to be updated so that the same state
will be reproduced when Tomcat is restarted.

Right now, though, you have to redeploy the next time you start Tomcat.
Fortunately, you need to do that less and less nowdays ...

>
> Thanks
> Bry
>

Craig


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Re: Persistent Context names with auto-deploy

[bryan collins]

I am using manager for the intial deployment of an app.
I don't want to have to re-deploy the apps each time TC starts up.

Is there a way for TC to remember what path you deployed an app on via
the manager app?
Keep in mind that unpackwars=true must be set for filesystem access.


Thanks
Bry

Jeff Larsen said:
[ Charset ISO-8859-1 unsupported, converting... ]
> Since you are using the manager app to deploy your war files, there is no 
> need to keep the war files in the webapps directory. Make a separate
> directory outside of /www/webapps, perhaps /www/war. Then Tomcat
> won't find them when it starts up.
> 
> Jeff
> 
> 
> - Original Message - 
> From: "bryan collins" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, April 10, 2002 12:15 AM
> Subject: Persistent Context names with auto-deploy
> 
> 
> > Hi,
> > 
> > I have an environment that serves requests via apache, on Solaris.
> > I have configured Tomcat 4.0.3 with mod_jk, most things appear to be working
> > just fine.
> > 
> > Apache is configured to pass /apps/* to tomcat via ajp13 protocol.
> > Tomcat is configured with an appbase of /www/webapps
> > 
> > I automatically deploy my .war files on paths of /apps/servletname
> > so I can have completely independant contexts for each servlet.
> > 
> > This works, and I can access the app via apache.
> > However, when tomcat restarts, it finds the servlet in the appbase, since
> > unpackWARS=true, and automatically deploys it under /
> > 
> > My question is, How can I force persistance of Context paths across a Tomcat
> > restart, when using automatic deploy (via the manager app)
> > 
> > i.e
> > auto-deploy foo.war on /apps/foo (via manager)
> > TC extracts the war to /www/webapps/foo, everything works perfectly.
> > After TC restart, TC deploys the servlet as /foo, not /apps/foo.
> > 
> > Any ideas?
> > 
> > Many Thanks
> > Bry
> > 
> > --
> > To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> > For additional commands: <mailto:[EMAIL PROTECTED]>
> > Troubles with the list: <mailto:[EMAIL PROTECTED]>
> 
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
> 

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Re: Persistent Context names with auto-deploy

[Jeff Larsen]

Since you are using the manager app to deploy your war files, there is no 
need to keep the war files in the webapps directory. Make a separate
directory outside of /www/webapps, perhaps /www/war. Then Tomcat
won't find them when it starts up.

Jeff


- Original Message - 
From: "bryan collins" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 10, 2002 12:15 AM
Subject: Persistent Context names with auto-deploy


> Hi,
> 
> I have an environment that serves requests via apache, on Solaris.
> I have configured Tomcat 4.0.3 with mod_jk, most things appear to be working
> just fine.
> 
> Apache is configured to pass /apps/* to tomcat via ajp13 protocol.
> Tomcat is configured with an appbase of /www/webapps
> 
> I automatically deploy my .war files on paths of /apps/servletname
> so I can have completely independant contexts for each servlet.
> 
> This works, and I can access the app via apache.
> However, when tomcat restarts, it finds the servlet in the appbase, since
> unpackWARS=true, and automatically deploys it under /
> 
> My question is, How can I force persistance of Context paths across a Tomcat
> restart, when using automatic deploy (via the manager app)
> 
> i.e
> auto-deploy foo.war on /apps/foo (via manager)
> TC extracts the war to /www/webapps/foo, everything works perfectly.
> After TC restart, TC deploys the servlet as /foo, not /apps/foo.
> 
> Any ideas?
> 
> Many Thanks
> Bry
> 
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Persistent Context names with auto-deploy

[bryan collins]

Hi,

I have an environment that serves requests via apache, on Solaris.
I have configured Tomcat 4.0.3 with mod_jk, most things appear to be working
just fine.

Apache is configured to pass /apps/* to tomcat via ajp13 protocol.
Tomcat is configured with an appbase of /www/webapps

I automatically deploy my .war files on paths of /apps/servletname
so I can have completely independant contexts for each servlet.

This works, and I can access the app via apache.
However, when tomcat restarts, it finds the servlet in the appbase, since
unpackWARS=true, and automatically deploys it under /

My question is, How can I force persistance of Context paths across a Tomcat
restart, when using automatic deploy (via the manager app)

i.e
auto-deploy foo.war on /apps/foo (via manager)
TC extracts the war to /www/webapps/foo, everything works perfectly.
After TC restart, TC deploys the servlet as /foo, not /apps/foo.

Any ideas?

Many Thanks
Bry

--
To unsubscribe:   
For additional commands: 
Troubles with the list: