On 26/08/2011 19:21, Johannes Ernst wrote: >> The documentation has to be updated. Please file an issue. > > https://issues.apache.org/bugzilla/show_bug.cgi?id=51727 > > Personally I feel the documentation is correct and the code is wrong. What > point is there to have a path parameter in context.xml if it has to be > specified (redundantly) as a URL argument as well?
If you read the Context documentation, you'll see that the path attribute isn't valid in most deployment configurations - only in the case that the Context is defined in server.xml. Since the deployer doesn't add the Context to server.xml, the path attribute isn't valid. Parsing the context file to extract the path might be an option, but seems like a lot of effort given that setting a parameter solves the problem and is really inexpensive. p > I'd like to be able to say > .../deploy?config=mycontext.xml > > and then also, symmetrically: > .../undeploy?config=mycontext.xml > > This API makes a lot more sense IMHO. </soapbox> ;-) > > Thanks for your help. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
signature.asc
Description: OpenPGP digital signature
