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

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-3575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3575.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5-RC4
                   1.4.18
         Assignee: Martin Grigorov

> ResourceLink uses the wrong PageMap, if used as a PopupLink
> -----------------------------------------------------------
>
>                 Key: WICKET-3575
>                 URL: https://issues.apache.org/jira/browse/WICKET-3575
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 1.4.15
>         Environment: Mac Os / Windows, tomcat 5.5, Java 5
>            Reporter: Olaf Siefart
>            Assignee: Martin Grigorov
>              Labels: PageMap, Popup, ResourceLink
>             Fix For: 1.4.18, 1.5-RC4
>
>   Original Estimate: 0.25h
>  Remaining Estimate: 0.25h
>
> 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

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira