On Tue, Jul 13, 2004 at 08:12:23AM -0700, Hubert Rabago wrote: > --- Ding Lei <[EMAIL PROTECTED]> wrote: > > > > Hi Hubert, > > Thanks for your reply first .. but: > > > > On Mon, Jul 12, 2004 at 09:32:45PM -0700, Hubert Rabago wrote: > > > This is really how it's designed to work. For a form to be resubmitted, > > the > > > user will have to regenerate the form, maybe by going back two pages, to > > the > > > page that was shown *before* the form. As you might already know, this > > > protects against accidental double submits. > > > > Yes, the problem is that even if the form is regenerated, it is STILL USING > > THE SAME REQUEST object, which means that the token still stays there. > > This suggests that either your Action is not being called (the form is being > cached by the browser or the server), or you missed the call to > saveToken(request). IMHO, the saveToken(request) IS CALLED for sure. It's actually the opposite, the token is saved, but never "resest" anywhere.
A simple "refresh" problem is becoming more and more complicated, perhaps a uniqueness check on user ID upon creation is the easiest way to to avoid duplicate records. Thanks for all of your help, anyway. -- Layman <[EMAIL PROTECTED]> Ext: 8059 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
