Wicket
  1. Wicket
  2. WICKET-3575

ResourceLink uses the wrong PageMap, if used as a PopupLink

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.15
    • Fix Version/s: 1.4.18, 1.5-RC4
    • Component/s: wicket
    • Environment:
      Mac Os / Windows, tomcat 5.5, Java 5

      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

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Martin Grigorov
            Reporter:
            Olaf Siefart
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 0.25h
              0.25h
              Remaining:
              Remaining Estimate - 0.25h
              0.25h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development