[
https://issues.apache.org/jira/browse/WICKET-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852840#comment-13852840
]
Sven Meier edited comment on WICKET-5426 at 12/19/13 12:06 PM:
---------------------------------------------------------------
Now as to the actual problem...
Page#onBeforeRender() resets the cached stateless already:
{code:java}
@Override
protected void onBeforeRender()
{
...
// if the page is stateless, reset the flag so that it is tested again
if (Boolean.TRUE.equals(stateless))
{
stateless = null;
}
...
}
{code}
Why don't we do this for FALSE too? This would fix this issue.
was (Author: svenmeier):
Now as to the actual problem...
Page#onBeforeRender() resets the cached stateless already:
@Override
protected void onBeforeRender()
{
...
// if the page is stateless, reset the flag so that it is
tested again
if (Boolean.TRUE.equals(stateless))
{
stateless = null;
}
...
}
Why don't we do this for FALSE too? This would fix this issue.
> Page not recognized as stateless although stateful component is hidden in
> #onConfigure()
> ----------------------------------------------------------------------------------------
>
> Key: WICKET-5426
> URL: https://issues.apache.org/jira/browse/WICKET-5426
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.12.0, 7.0.0
> Reporter: Sven Meier
> Priority: Minor
>
> Page#stateless gets cached. If Page#isStateless() is called before rendering,
> a page might not be considered stateless although in #onConfigure() all
> stateful components are hidden.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
