https://issues.apache.org/bugzilla/show_bug.cgi?id=54642
Bug ID: 54642
Summary: HostConfig undeployApps missing, no way to define
apps' undeploy order.
Product: Tomcat 7
Version: 7.0.37
Hardware: PC
Status: NEW
Severity: minor
Priority: P2
Component: Catalina
Assignee: dev@tomcat.apache.org
Reporter: eugene.ma...@gmail.com
Classification: Unclassified
Prior to HostConfig#7.0.3 it had undeloyApps() called in its stop() method.
That gave nice opportunity (ootb, no custom changes) to have Context configured
in server.xml to be undeployed only after other Context's (from xmlBase, etc)
are undeployed. Here actually HostConfig.undeployApps() was undeploying these
xmbBase' apps, whereas remaining app from server.xml was undeployed later
(afair with StandardHost).
And starting with HostConfig#7.0.3 undeployApps() method is removed and nothing
similar is invoked from stop() method. And now any Context is undeployed just
as it comes in HashMap in ContainerBase at once (i.e. no 'pre' undeploying with
HostConfig).
So why such change was performed? Could you please say is there another
opportunity to control undeploy order (it is useful for me to have some control
over cooperating apps)? I'd like to have described behavior returned back.
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
