Therefore the filter does:
setLastServlet(((HttpServletRequest)request).getServletPath());
and then the filter invokes the servlet wtih a wrapper around its request
The wrapper overrides the public Object getAttribute(String name)
and only gives access to the attribute with name 'name' if the servlet which is called has the right path for that attribute. Therefore the wrapper needs to now the 'LastServlet'.
(So the problem is that the filter is only invoked at the beginning of the request. When a servlet does dispatcher.include, the setLastServlet of the filter won't be called anymore, and the "LastServlet" isn't the correct one anymore)
--------------------------
Interesting issue. Anyway, can't think of anything that solves it in a clean
way.
If you give me (if you can) further information about what your filter does,
I could give it a try at thinking about an alternative solution.
Cheers,
F.
_________________________________________________________________
Koop geen kat in een zak. Probeer alles 14 dagen bij jou thuis. http://linkstat.neckermann.de/go.mb1?benl_11294
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
