Hi, I have been using panel replacement instead of multiple different pages as a way to avoid a kind of back button problem but I am not happy with my solution.
The objective is to prevent the user from going back after an update to previous pages/versions of the page containing state of domain data which really does not exist anymore. This worked without AJAX when using HybridUrlCodingStrategy. Because of a high number of pages, I want to get away from any WebRequestCodingStrategy because of the Performance hint in IRequestTargetUrlCodingStrategy#getMountEncoder. I don't mind ugly URLs. When I remove the HybridUrlCodingStrategy then the approach does not seem to work anymore. Also I am suspicous of any missing panel crashes on navigation with the panel replacement approach. How can I meet my objective? Is there a Wicket best practice approach for this? I feel I am running round in circles considering options such as IRequestCycleSettings.RenderStrategy, setVersioned(false). My possibly oversimplified thought is that Wicket keeps changing page state on the server and via HTTP post redirect back to the same page there would never be a browser back option because the same page cannot have multiple subsequent entries in the browser history. I feel that this is such an obvious and common problem - I hope this has already been written about and I just missed the article. Many thanks, Bernard --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
