On 1/18/06, Joe Germuska <[EMAIL PROTECTED]> wrote: > >but I wonder if that's a good idea. > >Am I missing something here? Is there a way to ensure that the > >action is called each time with the set of parameters it was > >supposed to receive? > > If your forms are request scoped, there should be no problem; a new > object would be created each time. > > If you must use session scoped forms, it's not so easy, as the > "token" mechanism for dealing with "double-posts" is not automatic; > you must invoke it from your action, which means that the > population/corruption may have already happened.
Token is unrelated to this problem. Token prevents double submit (on server level). What he has is "populate, populate, execute, execute" instead of "populate, execute, populate, execute". The synchronization is definetely in order, but on a session, not on a form, I guess. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
