Re: Wicket back button behavior

2017-04-10 Thread Entropy
Hmmm, it's not quite PERFECTLY what I was after, but it may be "close enough". When I go back, I am still taken to previous pages by virtue of the mounted URLs, but I am no longer being taken to old VERSIONS of those pages, which was the main problem. I'll have to check with my requirements

Re: Wicket back button behavior

2017-04-10 Thread Zala Pierre GOUPIL
Hi, If I get you right, you want to be able to have some pages that always display their last state, right? What about trying the "Wicket no version mapper" pattern? [1] For you, getting rid of the version number in the URL is just a side-effect, but it should do the trick. Plus, you can switch

Re: Wicket back button behavior

2017-04-10 Thread Entropy
I am trying to set this up. I looked at some docs and I feel like creating a custom PageManager seems like what I want to do. The thing is, no matter how I implement the getPage(int), the Wicket app behaves the same. The back button still does it's default behavior every time. Here's what I

Re: Wicket back button behavior

2017-04-04 Thread Martin Grigorov
Hi, The Wicket way would be to roll your own IPageManager or IPageStore or IDiskStore and implement #getPage(int pageId) in a such way so that it always returns the last used page by the user (i.e. session). You may use https://github.com/martin-g/single-page-instance as an inspiration.