Re: Catch-all URL mapping logic

Excellent. Big thanks! (For any future reader, I needed to wrap the page in a PageProvider in the return statement.) I also managed to render nice corresponding URLs for BookmarkablePageRequestHandler in the mapHandler method. I then used the code posted at [1] to avoid redirects and keep the

Wicket back button behavior

By default wicket does it's serialized back button thing. For most of our apps, this has been fine. We have a new one where this behavior, showing the page in a previous state and allowing the user to proceed from there, is completely inappropriate. Ideally, when a user tries to go back to a

Re: Catch-all URL mapping logic

Hi, You can use a custom root request mapper! In YourApplication#init(): old = application.getRootRequestMapper() application.setRootRequestMapper(new CustomRequestMapper(old)) In CustomRequestMapper#mapRequest() first use 'old' to try to return IRequestHandler. If it returns null then use

Re: ComponentNotFoundException and Clustering failover

Hi, On Thu, Mar 30, 2017 at 11:21 PM, Wayne W wrote: > Please ignore my last email I have done a lot more debugging and I *think* > I understand why replication does not work for us: > > > Whenever a stateful pages is used (touched) the SessionEntry is updated, > >