Bug 168656
| Summary: | tomcat ignores deeper path in context.xml | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Application Server | Reporter: | KSRZIS <sys_admin> |
| Component: | tomcat | Assignee: | Fernando Nasser <fnasser> |
| Status: | CLOSED UPSTREAM | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-11-04 18:56:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
KSRZIS
2005-09-19 07:27:43 UTC
Hi, Can you be more specific about "tomcat5 from AS1", please? What is it, which version release, how and where was it downloaded from, how was it built if not downloaded as binary etc. Thanks. Fernando It was tomcat5-5.0.28-2jpp_5rh.noarch.rpm from Red Hat Application Server 1.0 (AS for i386) that I was experimenting with before availability of Application Server 2. In this tag you have
<Context docBase="/var/www/html/snzr/piv" path="/nsnzr/piv">
^^^^ ^^^^^
Doesn't the path have to match the docBase? Actually, wouldn't the path be
inferred from the value of docBase if it was just omitted? In any case, just
make sure the endings overlap.
I do not think they have to match. First because it worked this way in 5.0, second I havent found it in documentation (the only part about matching is that request URI is matched against path attribute) and third I've just tried it: <Context docBase="/var/www/html/psnzr/piv" path="/psnzr/piv"> and made a link in html psnzr -> snzr. Same result as before. In server.xml, it works as expected. Thanks for trying anyway. We will have to run some experiments here. I will get back to you as soon as possible. According to the documentation for tomcat 5.5: "The value of this field (path) must not be set except when statically defining a Context in server.xml, as it will be infered from the filenames used for either the .xml context file or the docBase."[1] This did not exist in tomcat 5.0.X previously and I have posted a message on tomcat's developer list asking for an explanation for this change. However, as it stands it is clear that this is expected behaviour. Depending on the name of your xml file, the context name would be inferred, but not for deeper contexts. From these lines in the documentation it seems your work around of editing this in the server.xml seems like the only solution at the moment. Footnotes: 1: http://tomcat.apache.org/tomcat-5.5-doc/config/context.html OK, I have been bugging Tomcat folks about this and now I've got some more support from other people who are also annoyed by this. Someone is claiming that if you name the file nsnzr#piv.xml it should work I.e, one should replace the context path '/'s with '#'s (no leading '#'). It is a documentation ommission, it is claimed. I am trying to get confirmation on this, but if any of you want to give it a try and let the others know it would be nice. For reference, this is the bug created by Oded. Please vote if possible, and comment if you have preferences about the way it is handled: http://issues.apache.org/bugzilla/show_bug.cgi?id=38198 Thank you. The # solution works fine, which is good. I am moving to apache's bugzilla to help to solve this problem. Adding reference to the upstream bug and changing the resolution to UPSTREAM, where this should be fixed/clarified. |