[
https://issues.apache.org/jira/browse/WICKET-5083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636205#comment-13636205
]
Sven Meier commented on WICKET-5083:
------------------------------------
Hi Martin,
will you revert the revert (af890025eb8fd12459600cf2cf93bc78661589f4) too?
diff --git a/wicket-core/src/main/java/org/apache/wicket/Page.java
b/wicket-core/src/main/java/org/apache/wicket/Page.java
index 86c0472..1467798 100644
--- a/wicket-core/src/main/java/org/apache/wicket/Page.java
+++ b/wicket-core/src/main/java/org/apache/wicket/Page.java
@@ -450,8 +450,6 @@
if (stateless == null)
{
- internalInitialize();
-
if (isStateless() == false)
{
stateless = Boolean.FALSE;
> Page#isPageStateless() may return wrong value
> ---------------------------------------------
>
> Key: WICKET-5083
> URL: https://issues.apache.org/jira/browse/WICKET-5083
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.6.0
> Reporter: Christoph Leiter
> Assignee: Martin Grigorov
> Fix For: 6.8.0
>
>
> This ticket is a follow up to WICKET-5078 (WICKET-4763 also seems related).
> Page#isPageStateless() can be invoked at a time where onInitialize() hasn't
> been called yet. This causes pages to report that they are not stateful, even
> though they are, if the stateful components are added in onInitialize() and
> not in the constructor.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
