On Fri, Nov 14, 2008 at 9:36 PM, Mark Derricutt <[EMAIL PROTECTED]> wrote: > It was actually the servlet mapping issue that was the problem - as it > causes Apache Sling to no longer work. > > Which spec were you looking at? Reading through > http://jetty.mortbay.org/jetty5/faq/faq_s_500-Servlets_t_Path%20Mapping.html: > > Path Spec: / > > Will match: / path= info=/ > /path path= info=/path > /path/ path= info=/path/ > /path/info path= info=/path/info > > /path/info.jsp path= info=/path/info.jsp > > /other path= info=/other > > From the ticket: "if the same servlet is registered in exactly the same > manner to "/" and a request is made to "/foo/bar" the servlet path is set to > "/foo/bar" and the path info is null" which doesn't seem to match the above; > which implies that path should be "" and info "/foo/bar".
IIRC, the real problem is the OSGi spec (based on Servlet spec 2.1) is defining a resolution different from what Jetty does (which I assume is Servlet 2.5 spec). Pax Web needs to follow the OSGi spec, even though most other Http Service implementations don't at the moment. And that in turn creates a problem. Hopefully you will get a authorative answer from the CPEG soon. Cheers Niclas _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
