Re: Problem with saveToken(HttpServletRequest)

[Erik Weber]

Yes, my "input" attribute is set to the JSP I came from. Also I tried 
with and without the "path" attribute to the exception element itself. 
No luck.

I am using 1.1. I wonder if this is the problem.
Where would the token field get "whacked" from? Whose field is it? There 
is nothing required of the form bean or the JSP itself to make this 
work, right?

Sheesh, I wonder if I should just implement my own synchronizer token. I 
can't upgrade to 1.2.

Thanks,
Erik
Bill Siggelkow wrote:
Erik Weber wrote:
Bill, my login action is almost identical to yours up until the 
forward element, but I *am* losing the token. You said you thought 
this might happen if I redirected back to the login page instead of 
forwarding, but I don't even know how I would do that . . .

What version of Struts are you using?
Erik
I am using Struts 1.2; I haven't tested this in 1.1 yet. Is your input 
attribute set to the JSP you came from? It could be redirected if you 
were specifying a path for the local exception that resulted in a 
redirect. If you are not specifying a path than the default exception 
handler uses:

ActionForward forward = mapping.getInputForward();
If you get stuck I would debug the puppy -- simply set a breakpoint in 
the ExceptionHandler's execute method and see if the token field is 
getting whacked.

Bill Siggelkow
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]