I don't fully understand why wicket needs to clone the page rather than just moving the page into the new page map?I believe Wicket does this so it can operate correctly no matter which path the user choose ( e.g. to continue in the new page, to still work in the old page, or both). Cloning (through serialisation) the page makes sure you have two copies of the state.Now, don't take that for the gospel (because as you can see I am just learning) but I believe it to be the case.
Yes that is it.
The page that you are showing now in a different window can also be displayed in another window.
So we can't move it because it also have to exist with its different versions in the pagemap it came from.
in the next version i will merge the branch i have where pagemaps and so on are a bit refactored and we store page/versions directly to disk.
So we have a snapshot for every page version. And we can go back to any of them when ever we want.
johan
