Re: Token Session Interceptor problems

Weird, I replied to the mailing list but it didn't go through... 


Hey Martin,

I don't get the time to read this mailing list as much as I used to,
sorry... I wrote the token handling stuff, so I'm probably the person
to talk to.

The invalid-token result shouldn't be needed for the token-session
interceptor. It's not going to send you to that result. What it does
is to save the action invocation, along with the previously executed
action, into the session. When a duplicate form post comes in, it
pulls the invocation out of the session based on the token value and
tells it to re-render the result without re-executing the action.

My first guess for your problem would be around serialization. When
that stuff is put in the session, it might / probably will be
serialized (depends on the container), and when it's pulled back out,
it will have to be deserialized. If there's stuff in your action (or
your action iteself) which are not serializable, it will cause
problems.

That's just a first guess... I'd recommend getting the source for
WebWork and trace through the interceptor and see exactly where it's
breaking.

Hope that helps,

Jason
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=53319&messageID=109469#109469