[WICKET-5068] PageParameters missing from re-created Page

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.4.0
• Fix Version/s: 7.0.0-M1
• Component/s: wicket
• Environment: All
• Assignee: Martin Tzvetanov Grigorov
• Reporter: bernard
• Created: 28/Feb/13 21:09
• Updated: 11/Aug/14 11:19
• Resolved: 16/Jan/14 10:56

Description

WICKET-4594 removes existing PageParameters when re-creating an expired page.

It does this under the assumption that the parameters are not needed for callback behavior that must not be executed after expiry.

However PageParameters are needed even without execution of callback behavior.

In trivial cases, a page cannot be re-constructed successfully without PageParameters e.g. a view page for a customer order needs the order ID from its PageParameters.

There is a bit of an irony about this. To improve the recovery behavior, i.e. to avoid the dreaded PageExpiryException, one needs to create some client state which is then lost on re-creation after expiry.

Issue Links

• Is contained by: WICKET-5008 PageProvider#getPageInstance() calls wrong Page Constructor if pageParameters is null
• relates to: WICKET-5001 Recovery of bookmarkable Page after Session Expiry
• relates to: WICKET-5539 Allow preserving of the parsed PageParameters when re-creating an expired page
• relates to: WICKET-5070 Optionally execute Callback Behavior on Re-construction after Expiry