Hi, We have a Single-Page-Application (SPA) with five pages. On page three we redirect to a payment partner. Once the payment is done, it redirects back to our application with given URL. Because I want to continue on page three, the URL contains the pageId. Sounds good so far. But now the payment partner has added a reference token to the URL and as described in this Ticket <https://issues.apache.org/jira/browse/WICKET-4441> , Wicket will create a new page instance because the PageParameter have changed.
What I want to do is that my application always uses the existing page, no matter if parameters have changed. I achieved this by adding a custom MountedMapper, which basically reverts this commit <https://fisheye.apache.org/changelog/wicket-git?cs=a53591f030b87b5d1552e567226705020dee2a62> In your opinion, is this the proper way for handling those kinds of problems, or are there any drawbacks to this approach? Thanks for your time, Ravi Ticket-4441 https://issues.apache.org/jira/browse/WICKET-4441. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Use-Page-from-Pagestore-even-if-PageParameters-have-changed-tp4676971.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
