On 2/8/07, Jan Vermeulen <[EMAIL PROTECTED]> wrote:
>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 ?
yes i first wanted it to test a bit in the 1.3 (so that i not have too constantly keep 2 branches up 2 date) I hope to do it this weekend
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'.
What you really should do is just generate the url to the current page. And then parse the url...and set the version to one lower then it is But i guess this is also not a happy situation :( And now in 1.3 or 2.0 there is no previous version at all if you just do ajax. so i hope that that previous button is an normal request and that your really want to go back to another normal request. johan
