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.
Anyway, if you still want to do that then extend org.apache.wicket.protocol.http.SecondLevelCacheSessionStore and hack around in org.apache.wicket.protocol.http.SecondLevelCacheSessionStore.SecondLevelCachePageVersionManager. You may need to copy/paste the whole stuff in your own class. Finally override org.apache.wicket.protocol.http.WebApplication.newSessionStore() to use your class. martin-g The destiny loves the braves! On Fri, Sep 17, 2010 at 1:35 PM, Gaetan Zoritchak < [email protected]> wrote: > I'm waiting for a long time for the resolution of this bug wich is very > important in regards on the use of Ajax nowadays. Unfortunately, the > resolution has always been delayed and I don't know enough Wicket to try to > resolve it. :( > > 2010/9/17 Josh Kamau <[email protected]> > > > hello, Is there a way of updating the page version after an ajax request > in > > order to support the back button for a 100% component based application > > (i.e > > an application based on a single page)? > > > > i think my question is related to this > > https://issues.apache.org/jira/browse/WICKET-271. > > > > Has any of the 1.5 milestones implemented this? > > > > kind regards. > > Josh > > >
