On 13/03/2010 14:09, Guilherme Rios wrote:
1. Are the calls to "addServiced(path)" (line 1362) and
"removeServiced(path.replace('#','/'))" (1386) there just to keep
someone else to try and undeploy the app while we are already doing it
Yes.
or do they serve some other purpose?
No.
2. Why calling "check(path.replace('#', '/'))" at line 1384? Would
undeploy work just the same without this call?
Support for contexts with paths of the form /foo/bar.
Tomcat converts this to foo#bar when it creates the directory.
3. Is undeploying, at least as far as ManagerServlet and classes
operating at the same layer are concerned, just about erasing the app's
WAR file, or its directory if there is no WAR, or its config file if
there is neither?
There is a little more to it. The various components (Servlets, Filters,
context etc) are stopped which triggers things like
ServletContextListeners and - if all goes to plan - allows the resources
to be GC'd.
I ran a few tests and noticed code that just erases the relevant
files does work, but really seem overly simplistic, so now am asking
myself where to draw the line.
Look at the StandardContext.stop() method if you want to understand
things in more detail.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
