Mark Thomas wrote:
André Warnier wrote:
Now comes the basic question : can a webapp stop itself, without taking
the whole Tomcat and JVM with it ? In other words, in response to
something (a variable being a certain value, or the interception of some
event or whatever), can my webapp decide to stop doing what it is
currently doing, clean up after itself, and then do something to prevent
itself ever being called again in the future of this Tomcat instance ?
(or say at least until some external intervention activates it again).
Yes. It should be able to ask the manager to stop it or undeploy it.
If I am not abusing, how does it do that, schematically ? I presume it
has a more direct way than to itself isue a HTTP request to the Manager
webapp with the appropriate parameters ?
And if it asks to undeploy itself, is it not like pulling the carpet
from under its own feet ? I mean, this webapp is running, and even
after asking the Manager to undeploy itself (meaning its whole shebang
of classes and libs will be erased from the disk), it should be able to
still stop itself cleanly. What if that requires a class that would
have to be loaded from its own WEB-INF/classes dir, which may not be
there anymore ?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
