the problem with "updating the version of the page" is that all urls in the page, be in hrefs or in javascript, have to be rewritten with the new page version...
-igor On Tue, Sep 21, 2010 at 2:19 AM, Josh Kamau <joshnet2...@gmail.com> wrote: > May be you could provide the developer with access to the page history > utilities such that i can update the version of the current page at will or > leave things to work normally if i dont want to break anything. something > like thisPage.getVersion().increment() ; > > regards. > > On Fri, Sep 17, 2010 at 6:03 PM, Martijn Dashorst < > martijn.dasho...@gmail.com> wrote: > >> On Fri, Sep 17, 2010 at 3:04 PM, Martin Grigorov <mgrigo...@apache.org> >> wrote: >> > I wont say this is a bug. >> > Actually it is by design. >> > When the page renders all links' href url points to specific page >> version. >> > So when the user clicks on any link the page is properly resolved and the >> > click processed. >> > If you change the page id with Ajax then there is a chance to leave >> broken >> > links/forms in the page. Clicking on those will result in either using >> old >> > version of the page or even worse PageExpiredException. >> >> Couldn't we use a cookie to keep the current version/tab/window? we >> could update it serverside and clientside to our liking... Not sure >> how we could hook into the back button for that though... >> >> One thing is sure: when using ajax, javascript works... >> >> Martijn >> >> --------------------------------------------------------------------- >> 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
