-
1. Re: Filter and servlet mappings
j2ee_junkie Jul 13, 2006 11:49 AM (in response to adamw)Adam,
That is the behavior defined by the servlet spec. If you want a filter on that resource to be invoked, then you need to use re-direct, not forward.
cgriffith -
2. Re: Filter and servlet mappings
adamw Jul 13, 2006 11:52 AM (in response to adamw)OK, thanks.
--
Adam -
3. Re: Filter and servlet mappings
adamw Jul 13, 2006 11:57 AM (in response to adamw)Hello,
I'm still wondering tho, why does it work if the servlet is mapped to a more specific path - like /xxx/* - then the forwards work as they should.
--
Cheers,
Ada -
4. Re: Filter and servlet mappings
adamw Jul 13, 2006 12:32 PM (in response to adamw)Hello,
is there any way then to include a JSP page in a servlet, which is mapped to /*? I tried doing simply request.getRequestDispatcher("/mypage.jsp").include(request, response); but this invokes the servlet and causes a loop.
--
Cheers,
Adam -
5. Re: Filter and servlet mappings
adamw Jul 13, 2006 2:53 PM (in response to adamw)Hello,
I solved the problem by mapping the servlet to /, and thus making it the default servlet. Then the requests for the JSP page go where they shold. Though I thught that when there are two overlapping mappings specified, one more and one less specific, the more specific is used in case of an path that matches both.
--
Cheers,
Adam