On 5/31/06, CrackheadMillionaire <[EMAIL PROTECTED]> wrote:
I recently implemented a filter to push some information into the session. Great.
However, after filter processing and within my DispatchAction, if I make a call to
request.getSession().getAttribute("whateverName"); the values aren't there; in
fact, the session attached to my incoming request is null.
That would seem to indicate that your Filter isn't being executed, or
isn't doing what you think it's doing. Without more information, like
sample code, your Filter mapping, etc., it's hard to tell.
I have this code in a Filter, with no problems, and the object is
always there when I retrieve it later in an Action:
request.getSession().setAttribute( Constants.USER_KEY, webUser );
Also, can anyone explain why my filter is bypassed if the mapping is for
*.jsp, but gets hit for *.do?
Probably because the original request was for someAction.do, and then
you're _forwarding_ to the JSP on the server side. The Servlet 2.4
spec introduced some new options for filter mapping. What version are
you using (or what version of what container)?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
