> Ok, I have found the problem. It is a result of an incorrectly written piece > of code in StandardContextMapper.map() under // Rule 3 > > I'm working on a rewrite that will parse things the way that they should be > parsed. :-) The issue is that the relativeURI variable can be pretty much > anything so it is difficult to figure out what the actual file suffix is out > of the path... > > Some initial testing shows that the relativeURI variable could be any number > of bits of information... > > uri: /Links.vm > uri: /Links.vm/foo/bar > uri: /Links.vm;foo/bar > uri: /Links.vm:foo/bar > uri: /Links.vm.foo/bar > > So, what I'm going to do is start at the first "." and then attempt to > resolve each additional character in the URI after the period against the > context.findServletMapping() until a match is found or the end of the URI is > reached.
Mmmm, I'm not too sure about all this. The servlet spec seems to imply that the extension mapping is on the end of the path. Section 11.1, item #3 : If the last segment in the URL path contains an extension (e.g. .jsp), the servlet container will try to match a servlet that handles requests for the extension. An extension is defined as the part of the last segment after the last '.' character. Remy
