[ https://issues.apache.org/jira/browse/WICKET-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703119#comment-16703119 ]
Thomas Heigl edited comment on WICKET-6616 at 11/29/18 12:56 PM: ----------------------------------------------------------------- Attached quickstart with test that passes in 8.1.0 and fails in 8.2.0. The test only passes if the target component cannot be resolved immediately. So if I add the form in the constructor, instead of in {{onInitialize}}, the test fails in 8.1.0 as well. was (Author: thomas.heigl): Attached quickstart with test that passes in 8.1.0 and fails in 8.2.0. The test only fails if the target component cannot be resolved immediately. So if I add the form in the constructor, instead of in {{onInitialize}}, the test passes in 8.2.0 as well. > Stateless pages are not rendered anymore before executing a behavior > -------------------------------------------------------------------- > > Key: WICKET-6616 > URL: https://issues.apache.org/jira/browse/WICKET-6616 > Project: Wicket > Issue Type: Bug > Components: wicket-core > Affects Versions: 8.2.0 > Reporter: Thomas Heigl > Priority: Major > Attachments: myproject.zip > > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)