Thanks, I saw this reference, but the problem is a bit other. As I said my page (version 1) is up-to-date, it shows correct info (therefore it doesn't need to be refreshed), but wicket doesn't create new version of the page.
So, if we abstract from the environment niceties the problem sounds like follow: there are created 0, 1, 2 versions of a page, after with back button the version 1 is made current. What should happen if I perform action that creates new version 2 of the page (should version 2 in PageMap be replaced with the new one or there should be two paralell versions 2 created). Because at the moment server performs all operations properly, but browser just shows version 1 (with the up-to-date state). Best regards, Vladyslav Oleniuk -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/action-on-an-old-versioned-page-tp2293075p2293315.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]
