Re: saveToken/isTokenValid

[Ted Husted <te...@gmail.com>]

The strategy only allows one token at a time for the application,
because the token is always given the same name. I believe Shale is
using another strategy that gives the tokens different names for
different workflows. If the popups are using tokens too (because they
have forms?), then you would have to code your own token strategy that
allows for use of different names for the token. If the popups use
forms, then it sounds like you might also be getting into wizard
space, where something like Struts Pageflow, or another wizard
extension, might help.

* http://struts.apache.org/struts-flow/index.html

-- HTH, Ted.
http://www.husted.com/poe/

On 12/29/05, Frank Maritato <fr...@eharmony.com> wrote:
> Hi,
>
> I have a form where the action uses the saveToken/isTokenValid pattern for
> preventing double submit. This page also has links that popup another page where
> the action uses saveToken/isTokenValid also (this page can be called stand-alone
> too, not always from popup link). Problem is that when the popup is dismissed,
> the token on the original page is no longer valid and the user has to submit the
> page 2x in order for isTokenValid to succeed. Anyone run into this? What is a
> good way to solve it?
>
> I'm using struts 1.2.4 on tomcat 5.0.28 and jdk 1.5.0_05.
>
> Thanks
> --
> Frank Maritato

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org