-
1. Re: Jetty HttpServletRequest.getServletPath() problem
gregwilkins Oct 3, 2002 2:27 PM (in response to ultracode)I assume that you have a servlet named "pending"?
I'm not sure if the spec is that clear what these
methods should report for a named servlet dispatch.
Jetty is reporting the returns for a match of the
invoker servlet at /context/servlet/*, and I don't
think the spec is very clear if this is correct or
not.
We use a request dispatcher to go from the invoker servlet to the named servlet. The spec does not say if the path methods should change for such a dispatch and we leave them as they are.
So I think your webapp is in a very ambiguous part of
the spec. But I will investigate further and ask the JSR 154 and watchdog folks what they think.
Probably we will change to match the tomcat behaviour.
cheers -
2. Re: Jetty HttpServletRequest.getServletPath() problem
mcmagnus Oct 24, 2002 11:03 AM (in response to ultracode)Any news regarding this?
I had the same problem moving Slide from Tomcat to JBoss. I patched Jetty's behaviour and now it works ok. But did you find any conclusive specs from JSR 154 and the "watchdog folks"?
Magnus -
3. Re: Jetty HttpServletRequest.getServletPath() problem
gregwilkins Oct 25, 2002 6:55 AM (in response to ultracode)
No i did not get any additional feedback - so I guess
we will have to follow tomcat.
What was the patch that you did? Was it a hack or generally applicable? Can you email it to gregw@mortbay.com.
thanks -
4. Re: Jetty HttpServletRequest.getServletPath() problem
gregwilkins Oct 25, 2002 7:49 AM (in response to ultracode)Here is an updated Invoker servlet that should work on Jetty 4.1 and Jetty 4.2. It should fix the problem (but a more efficient fix will come eventually).
cheers