Originally posted by Bear Bibeault:
Mapping /* is going to cause a lot of headaches, including the static resource issue. Why is it a requirement? What's wrong with having a reasonable servlet path? (E.g. /something/*).
I want to avoid having to actually open the file on the filesystem and stream it to the response.
Originally posted by William Brogden:
But thats what the default request handler does - one way or another it has to be done.
Essentially handling all /* means you are replacing the default handler - if this was my problem, and I was working with Tomcat, I would remove the default handler mapping and just forward all requests that did not require custom handling to it.
Bill
Originally posted by Darrin Holst:
I'm trying to solve the exact same problem, pretty frustrating how limiting the servlet mapping is. Anyway, I tried
<servlet-mapping>
<servlet-name>default</servlet-name>
<url-pattern>/images/*</url-pattern>
</servlet-mapping>
which stops sending it to my dispatcher, but I'm still getting a 404 on any image I request.
Originally posted by Dudley Dawson:
Well, you are getting the 404 becasue you have no servlet named "default" in your DD. I guess what we're both looking for is a way to invoke the default handler, either programmatically or declaratively.
[ September 30, 2008: Message edited by: Dudley Dawson ]
Originally posted by Darrin Holst:
I'm trying to solve the exact same problem, pretty frustrating how limiting the servlet mapping is. Anyway, I tried
<servlet-mapping>
<servlet-name>default</servlet-name>
<url-pattern>/images/*</url-pattern>
</servlet-mapping>
which stops sending it to my dispatcher, but I'm still getting a 404 on any image I request.
He puts the "turd" in "saturday". Speaking of which, have you smelled this tiny ad?
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
|