tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25948] - FIX: Manager App can't redeploy ROOT applications
Date Thu, 08 Jan 2004 10:40:46 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25948>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25948

FIX: Manager App can't redeploy ROOT applications





------- Additional Comments From pr@webapp.de  2004-01-08 10:40 -------
I found two more wrong undeploy parameter at ManagerServlet.

But following situation was strange:
Context Deployment with a context path="/" work also, but you can't undeploy 
those ROOT Context. The spezial ROOT context path handling with out "/" not 
working at the ContextRuleSet configured context. The result is the manager 
application can't find the ROOT application.
ManagerServlet unddeploy(..)
-...
    deployer.findDeployedApp("") # search for "" but the ROOT context is 
registerted under "/".

OK: The doc say set path to "" is the only way two set ROOT context but the 
ManagerServlet can load a context.xml with path "/" as ROOT context!

Strange...

Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message