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

Stateless pages are not rendered anymore before executing a behavior

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 8.2.0
    • Fix Version/s: 8.3.0
    • Component/s: wicket-core
    • Labels:
      None

      Description

      I just upgraded from 8.1.0 to 8.2.0 and a bunch of my tests broke. A required form component on a stateless page that is hidden in "onConfigure" started to report an error after the upgrade.

      The problem was introduced in WICKET-6608 by this commit:

      https://github.com/apache/wicket/commit/147f6d33f839edd9a6eb53ce9c20b4cde07fc938

      Previously, the page was initialized and rendered before returning the component. Now, for some reason, the page is initialized and the component returned immediately if it exists. This breaks all visibility/enabled conditions that are evaluated later in the life cycle of stateless components.

        Attachments

        1. myproject.zip
          26 kB
          Thomas Heigl

          Issue Links

            Activity

              People

              • Assignee:
                svenmeier Sven Meier
                Reporter:
                thomas.heigl Thomas Heigl
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: