Description of problem:
The A-Z application lives in its own webapp 'ccm-ldn-atoz', so when
requests for /ccm/atoz/ come in, BaseDispatcher tries to forward on to
the /ccm-ldn-atoz/ context. This works fine on Resin, however, on
Tomcat 4.0.6 it always results a 404. After much debugging I
discovered that the call
Web.getServletContext().getContext("/ccm-ldn-atoz/") is always
returning the root context. Very bogus, so I got out the Tomcat source
and looked at the getContext(String uri) method:

  String contextPath = context.getPath();

  if (!contextPath.endsWith("/"))
    contextPath = contextPath + "/";

  if ((contextPath.length() > 0) && 
      (uri.startsWith(contextPath))) {
    return (this);
  }

In pseudo code, this is doing:

  1. Get the current servlet context's path (ie, "" since this is the
ROOT)
  2. Append '/' to ensure that /foo doesn't match /foobar 
  3. If the request URI starts with current context path return
current context

Step 3 is where the fatal flaw is, because it means that you can
*NEVER* get hold of a servlet context mapped to a sub-URI of the
current context.

Since the ROOT context is mapped at "/", no matter what you pass in
you will always be given back the current context :-( This makes the
ServletContext#getContext(String uri) method useless and there is no
other API for getting a ServletContext.

This bug is not fixed until Tomcat 4.1.20 :-( 

http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-4.0/catalina/src/share/org/apache/catalina/core/ApplicationContext.java


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: