RE: Using saveToken and isTokenValid

2006-03-14 Thread Kalcevich, Daniel
What about putting the saveToken(request) at the bottom of the second action as well? This will put a new token into the request in the event you want to submit again. Dan -Original Message- From: starki78 [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 14, 2006 7:08 AM To: user

RE: Using saveToken and isTokenValid

2006-03-14 Thread starki78
Cc : Date : Tue, 14 Mar 2006 07:12:32 -0800 Subject : RE: Using saveToken and isTokenValid What about putting the saveToken(request) at the bottom of the second action as well? This will put a new token into the request in the event you want to submit again. Dan

Re: Using saveToken and isTokenValid

2006-03-14 Thread Dan Jas
@struts.apache.org Sent: Tuesday, March 14, 2006 10:53 AM Subject: RE: Using saveToken and isTokenValid Hi Thanks but my goal is just to tell the user that only the first submit shall be processed! My example works only partially Nice greetings -- Initial Header --- From : Kalcevich

Re: Using saveToken and isTokenValid

2006-03-14 Thread Emmanouil Batsis
In simple cases i just keep redirecting to the result view (and maybe warn the user) even if the token is invalid. The view is the result of the first submission anyway. Manos starki78 wrote: Hi Thanks but my goal is just to tell the user that only the first submit shall be processed! My

Re: Using saveToken and isTokenValid

2006-03-14 Thread starki78
Good Morning You have written: The view is the result of the first submission anyway. I cannot reproduce this! How cas I achieve that a submit is just replaced once! And that by several clicks the others are just ignored I cannot manage it! If I just forward to the success Configuration Objects