[
https://issues.apache.org/jira/browse/WICKET-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16704547#comment-16704547
]
Thomas Heigl commented on WICKET-6616:
--------------------------------------
The use-case in my test is very simple. On a stateful page, it works as
expected. On a stateless page it fails and as a developer I can't be sure if my
lifecycle callbacks will be executed or not. This makes it extremely hard to
reason about non-trivial (i.e. everything is added in the constructor)
stateless pages.
In my opinion, stateless pages should behave as much as stateful pages as
possible. I'd vote for always rendering them.
> 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)
