Re: action on an old versioned page
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 this message in context: http://apache-wicket.1842946.n4.nabble.com/action-on-an-old-versioned-page-tp2293075p2293886.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
action on an old versioned page
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 perform some action which leads to creating of a new version of the page. But it's not a case, e.g. the request is handled but any changes on the page are ignored and the version stays 1. The question are: Is it correct behaviour of the framework, and if it's, Where can I configure it so that new version 2 of the page would be created and replace the old v.2 in a PageMap. Thanks in advance. Best regards, Vladyslav Oleniuk -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/action-on-an-old-versioned-page-tp2293075p2293075.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: action on an old versioned page
not all actions on the page create new versions -igor On Sun, Jul 18, 2010 at 6:35 AM, Vlad Oleniuk vlad.olen...@gmail.com wrote: 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 perform some action which leads to creating of a new version of the page. But it's not a case, e.g. the request is handled but any changes on the page are ignored and the version stays 1. The question are: Is it correct behaviour of the framework, and if it's, Where can I configure it so that new version 2 of the page would be created and replace the old v.2 in a PageMap. Thanks in advance. Best regards, Vladyslav Oleniuk -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/action-on-an-old-versioned-page-tp2293075p2293075.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: action on an old versioned page
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, nevertheless web-browser shows version 1 of the page, however with up-to-date models of widgets. Could u explain to me (or give any reference), what is the expected behaviour of the framework in such a situation, and where it can be configured Thanks a lot. Best regards, Vladyslav Oleniuk -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/action-on-an-old-versioned-page-tp2293075p2293275.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: action on an old versioned page
i think this is what you are experiencing: http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/ -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/action-on-an-old-versioned-page-tp2293075p2293308.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: action on an old versioned page
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: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
