> From: André Warnier [mailto:a...@ice-sa.com]
> Caldarale, Charles R wrote:
> > That should be handled by a ServletContextListener declared
> in WEB-INF/web.xml, which will be invoked before the deletion
> of the webapp's files.
> >
> More seriously thus, there seems to be a problem with this logic :
> Suppose we have a case where 5 instances of this webapp are currently
> running
You can't have "5 instances" of one webapp, to my knowledge. You have one.
But I may not have seen some of the odder deployment scenarios.
> and one of them issues a request to the Manager, to undeploy
> itself. The Manager would then oblige, and start undeploying the
> webapp. The ServletContextListener in each
(i.e. the only one)
> of the running webapp
> instances would be called, before the Manager does anything drastic.
> Presumably then each ServletContextListener instance would
> have to take
> some action to force the corresponding webapp instance to stop and
> cleanup its act, and also presumably the Manager would wait
> for each of
> these instances to return some form of OK, before it proceeds with
> erasing the webapps files.
The file erase would not happen until the listener had returned. To my
knowledge, that's the only guarantee you get with such a listener.
- Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
