On 7/8/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > > From: Wendy Smoak <[EMAIL PROTECTED]> > > Sent: Jul 8, 2005 12:51 PM > > To: Struts Users Mailing List <user@struts.apache.org> > > Subject: Re: Passing data between action forms > > > > > From: "Michael Jouravlev" <[EMAIL PROTECTED]> > > > > > > It will sound like a scratched vinil, but I believe that forwarding > > > from search page to result page is not the right thing to do, because > > > whenever you refresh result page, you run the search query again. So, > > > it should be a redirect. > > > > I think so, too. I was just looking at the old project I wrote about, and I > > could dispense with setting those request attributes if I just constructed > > the URL to the ResolveName action, and redirected to it. Back then, I was > > just glad it worked. :) > > > > -- > > Wendy Smoak > > I'm not knocking your approach, but synchronizer tokens solve the same > problem, with or without a redirect. > > Erik
* You can catch resubmission in the application on server, but a user still sees POSTDATA message. This message is annoying, it gets in the way, and a user has to give an answer to a question which he does not understand, and what he should care less about. * What if I go back to the search page (which is in your case, is cached and is not reloaded, or so I presume) and resubmit the same or even a different query? Token was already removed from the session, so this would be considered as illegal resubmit. Using model to check for resubmit data is more robust and intelligent, than using tokens which know nothing about your data and workflow. Though tokens are better than nothing, of course. Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
