So you are worried about double submit, when using backbutton, of the same page that has invalid data? But if that happens then the second time has the same error as the first time.
On 1/24/08, Sam Hough <[EMAIL PROTECTED]> wrote: > > Igor, > > Am I at least correct that we shouldn't only commit at the end of request > processing as you might in struts? (because I need to know if the commit was > good before updating the page) > > I'm not really saying that you can't safely handle transactions and page > state in Wicket just sanity checking that I need to take more care? eg If > calling a method that may fail I shouldn't pass an argument that is attached > to the page that might be modified by that method before the commit works? > > I take your point that quite often we would just show the user an error page > but assuming we get the back button to work properly I think I need to > ensure the server side page is in a valid state. > > Thanks for the tip about Spring annotations, we were just using a single > commit at the end of the request. > > Cheers > > Sam > -- > View this message in context: > http://www.nabble.com/db-transaction-boundary-tp15042959p15060686.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
