Uploaded image for project: 'Wicket'
  1. Wicket
  2. WICKET-4875

AjaxLinks in Panels created by IComponentResolver do not work

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 6.3.0
    • None
    • wicket
    • None
    • Windows XP, Tomcat 6, JDK 1.6

    Description

      When a panel is added by an application provided implementation of IComponentResolver none of the AjaxLinkS work. When the same panel is added explicitly it works fine.

      I think it could be related to the change Wicket 6.x where all of the event handling code is added to a script in the <head> section instead of being distributed throughout the body where each AjaxLink is defined, like it was in Wicket 1.5.

      Attached is a quickstart that demonstrates the problem. It contains two instances of 'SystemPanel'. One is added explicitly in HomePage.java and the other is provided by the ComponentResolver.

      Clicking the first link will output a message to stdout/console. Clicking the second link will not because it's AjaxLink's onClick is not firing due to the bug.

      NOTE: attached quickstart uses port 80 not port 8080.

      Attachments

        1. resolverAjaxIssue.zip
          25 kB
          Chris Colman

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. WICKET-4408 Components resolved by an IComponentResolver fail to contribute to header via renderHead

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              svenmeier Sven Meier
              chrisc Chris Colman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: