[WICKET-5539] Allow preserving of the parsed PageParameters when re-creating an expired page

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 6.14.0
• Fix Version/s: 6.17.0
• Component/s: wicket
• Labels: expiration mountBookmarkablePage
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Ilia Naryzhny
• Created: 20/Mar/14 22:30
• Updated: 26/Aug/14 17:08
• Resolved: 12/Aug/14 08:51

Description

There is a bookmarkable page mounted, for example, to:
/page/${entityId}

This page contains StatelessForm.
Submitting of form after session expire lead to following:

org.apache.wicket.core.request.mapper.MountedMapper invokes AbstractBookmarkableMapper.processListener to obtain IRequestHandler to handle submitting of form.
But there is cleaning of PageParameters within processListener on line 256 (Wicket 6.14) which cleaning "entityId" parameter as well and created page finally has no "enityId" and (in our case) redirects to 404.

I see that this cleaning of page parameters was implemented due to Wicket-4594. But I think, just checking for pageId is unsufficient, because pageId might be not null, but actual page may be already expired and new instance should be created.

Issue Links

• is duplicated by: WICKET-5681 AbstractBookmarkableMapper sets pageParams to null, might be invalid
• is related to: WICKET-5001 Recovery of bookmarkable Page after Session Expiry
• is related to: WICKET-5068 PageParameters missing from re-created Page
• is related to: WICKET-5578 Stateless/Statefull pages - incorrect behaviour
• is related to: WICKET-5070 Optionally execute Callback Behavior on Re-construction after Expiry
• relates to: WICKET-4594 Do not use the parsed PageParameters when re-creating an expired page
• relates to: WICKET-5669 Mark page parameters with a flag where they have been read from
• links to: Latest Mail discussion at dev@ mailing list
• links to: Mail discussion at dev@ mailing list