After upgrading from Wicket 1.5 to Wicket 9, our users now may sometimes cause a Stale Page Exception by:

• Duplicating a tab
• Clicking a link, submitting a form, etc., in the second tab
• Returning to the first tab
• Trying to click a link, submit a form, etc., in the first tab

In the past, i.e. 1.5, Wicket's default behaviour on encountering a stale page exception was to recreate the original page. This gave the users a smooth and trouble-free experience, requiring just one extra click on the link or button in order to achieve their aim. They grew used to duplicating tabs, and wish to continue doing so.

Now, in Wicket 9, a stale page exception triggers a 500 error, which is seriously undesirable behaviour.

How can we return to the default behaviour that we had before? There must be a relevant setting somewhere, but I don't know where.

I would be most grateful if anyone can tell me how to change this setting. Thanks!

CodePudding user response：

This problem is solved by upgrading to Wicket 9.3.0 or later.