boris wrote:
> I know that it works according to the documentation but I can't
> ignore the fact that I believe it's wrong.
If you think the way Tomcat handles deployment is wrong, OK. But I don't think
you convince the developers (I'm not one, BTW) to change their point of view
by hijacking a
I know that it works according to the documentation but I can't
ignore the fact that I believe it's wrong. If you look closer in
the code of HostConfig.deployDescriptors() you note that others has
missed the ability to set the context path and has hidden it in the
filename which is neither portable
boris wrote:
> The problem
> is that the "path" attribute is ignored in the Context read from this
> directory. Only Contexts defined in the server.xml file honors the
> path attribute.
That's not a problem. It's exactly the way it's meant to be:
http://tomcat.apache.org/tomcat-6.0-doc/config/co
Problem:
The "path" attribute in the Context descriptor file no used in
TC 5.5 and 6.0.
Background:
In an application deployment you whish to be able to install and
upgrade both tomcat and your WARS individually. In TC 4.1 this was
easily done by dropping a Context descriptor file in the webapps
d
