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 38198] - When using context xml definitions standalone file, tomcat wrongly uses the file name instead the context path definition
Date Mon, 09 Jan 2006 16:23:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38198>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38198





------- Additional Comments From oded@m-wise.com  2006-01-09 17:23 -------
> RTFM. Especially the section in   
> http://tomcat.apache.org/tomcat-5.5-doc/config/context.html   
> that states:   
> "The value of this field [path] must not be set..it will be infered   
> from the filenames used for either the .xml context file or the docBase."   
   
I must say that though I have read that documentation several times I haven't   
actually read that paragraph - probably because the introduction paragraphs do   
an very good job of describing the path attribute and what it does, and the   
introduction does not say anything about guessing from the file name.    
Specifically the introduction says that context path MUST [sic] be used and   
then goes to great lengths explaining how contexts can be loaded from files,   
without ever mentioning to auto-guessing mechanism.   
   
I would also like to mention again that adhering to the path attribute is how   
tomcat have worked in all previous versions, its how everyone who upgrades to   
tomcat 5.5 would probably expect it to work, and it makes sense.    
   
> No, your statement is plain wrong. If you want to set the context path to  
> /some/path", name the XML file containing the Context definition  
> "some#path.xml".  
  
That is contrived. So basically you are saying that I can forget about having  
logical meaningful names to context files and instead I must use line noise to  
form complex structures ? That sounds like a regression to me.   
 
Might I suggest that for the sake of backward compatibility and for the peace 
of mind of people who are going to upgrade from 5.0 to 5.5, to support the 
path attribute if it exists and do the inferring only if it doesn't ?  
Also it might be a good idea to support a directory structure under 
cont/<engine name>/<host name>/ instead of coding directory separators into 
weird characters, chosen no doubt for their incompatibility with paths in URLs 
and not for readability and ease of use. 

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message