Yes, Pedro, putting things into Session would would work around this. But I
would need to put everything into Session manually. Isn't there any trick that
prohibits Components from being versioned? We don't need any backbutton support
at all. We jut want to keep the page the same unchanged
Hi, Stefan.
It might help to understand what you expect of Wicket: When the object in
Page 2 is updated and serialized into the page map, you expect Wicket to
know that it must also re-serialize Page 1 and Page 0 with the new object
state. The way this happens is simple: if the Page 2 object
