> > Or are you trying to deploy an updated war in place of an existing one?
>
> The latter. Our WAR files are deployed on a read-only (from the
> container's viewpoint) AFS file system. Our standard operating
> procedure with ServletExec when a web app is updated is to push out a
> new WAR file and then make the container aware of it via the "reload
> app" feature of the admin interface. Sometimes the path name to the
> WAR file changes, and sometimes not (we use symlinks extensively), but
> this has never been an issue with SE.
>


> > Try stopping an app. Remove it and then deploy the replacement.
>
> Now, that (stopping, removing, and re-installing) works. Thanks. The
> problem is that this is hardly a simple one or two click operation in
> the Manager app. Removing is, but reinstalling via the app is longer
> and more error-prone and requires you to know and to type in the
> location (using a URL) of the <Context> stub that describes the app.
>

Unless there is something I am missing on your setups try this:

In the manager for one of the apps click on remove. (It actually does the
stop for you.)
Then go down the page to the next section where all you do is specify the
path to your war file.
This will deploy the war into a folder named the same as the war file.


> We were hoping to find that there's some Tomcat configuration (perhaps
> of the JspServlet, perhaps of some other piece) that will defeat the
> bogus caching that's going on in the "work" directory and permit
> something as simple as a stop/restart sequence to work for WAR file
> redeployment.
>

I know that this has been discussed on the list before, but I don't know the
solution if any.

From the sound of things it would be worth your while to move up to TC5.
Then a simple remove and straight deploy from war would work fine with most
setups as your <context> stub is part of the war.

Doug



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@(protected)
For additional commands, e-mail: tomcat-user-help@(protected)