>This would work fine now i guess in the latest code of 1.3 >But that is because a page version is now always a different instance. >Because we don't rollback anymore >the same page instance (there is no changelist anymore)
We're working with the Wicket 2.0 trunk. Will these changes of 1.3 be applied to 2.0 ? >But this will not work when you use the accessstackpagemap (the normal >httpsessionstore impl) >Because then what happens is that the current page is changed underneath >your own call. >that could really result in all kind of strange things. We actually are having all kinds of strange behavior because of changes to the current page: we are programmatically doing back-button behaviour by retrieving the previous page/version pair from the pageStore. This is causing problems due to the fact that we have only one page: so the undo is applied to the same page instance that is being changed due to submit. So is it a bad practice to simulate this back-button behaviour in buttons within the page ? We have a lot of pages where 'exit' or 'cancel' buttons mean 'go back to the previous page'. >I also don't know if currentversionnumber-1 is the right page you want. >Because if the version number is already increased before that onsubmit call >(not very likely) >then -1 is the page you just got from and not the page before that. I know. I used RequestParameters.getVersionNumber() in some other test. The result is different if you change the input. -- View this message in context: http://www.nabble.com/Single-page-applications%3A-bad-idea-in-Wicket---tf3182341.html#a8867182 Sent from the Wicket - Dev mailing list archive at Nabble.com.
