[WICKET-3575] ResourceLink uses the wrong PageMap, if used as a PopupLink

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.15
• Fix Version/s: 1.4.18, 1.5-RC4
• Component/s: wicket
• Labels: PageMap Popup ResourceLink
• Environment: Mac Os / Windows, tomcat 5.5, Java 5
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Olaf Siefart
• Created: 29/Mar/11 13:34
• Updated: 04/Apr/11 12:28
• Resolved: 04/Apr/11 12:28

Description

If a ResourceLink is used with PopupSettings (in our case a custom PdfPopupLink) the target page is created in the main pagemap (name=null) and not in the pagemap from the PopupSettings. This is caused by not calling the isLinkClicked()-Method from the onResourceRequested()-Method in the ResourceLink-Class. The PageMap-Name is not set to the RequestParameters and so wicket uses the main pagemap.

If using an AccessStackPageMap the WebRequestCycleProcessor will now ignore every AjaxRequest from the original page, because the original page is no longer on top of the access stack.

Solution: calling onLinkClicked() instead of onClick in onResourceRequested()-Method of the ResourceLink