Thanks to everyone, who took part in the discussion.
The problem was in another aspect, page version 1 had a form, and the
framework didn't allow to resubmit it, hence recreate version 2, after
setting renderStrategy as ONE_PASS_RENDER everything works.
Best regards, Vladyslav Oleniuk
--
View
Hello all,
I have the problem with new page version creating from the older version of
the same page.
So, there is a page with id==x. Versions 0, 1 and 2 are sequentially
created.
After (being on the page with version==2) browser back button is pressed (go
to the version 1) and is tried to
Thanks for the answer,
yes, I understand it, but in my case it does, it creates new version.
Action on the page version 1 after returning to it from version 2 causes to
replacing one panel with the other one, and the interesting thing, that
debuging shows it works as it should, but,
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
