You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Christoph Leiter (JIRA)" <ji...@apache.org> on 2012/09/14 17:59:07 UTC
[jira] [Created] (WICKET-4763) RenderPerformanceListener causes
session creation
Christoph Leiter created WICKET-4763:
----------------------------------------
Summary: RenderPerformanceListener causes session creation
Key: WICKET-4763
URL: https://issues.apache.org/jira/browse/WICKET-4763
Project: Wicket
Issue Type: Bug
Components: wicket-devutils
Affects Versions: 6.0.0
Reporter: Christoph Leiter
Priority: Minor
If RenderPerformanceListener is active then sessions will be created even for stateless pages. This happens because RPL is an IComponentInstantiationListener which adds a Behavior to every component. That causes a call to addStateChange() which in turns calls AbstractPageManager#touchPage. At this point #isPageStateless always returns false (!) and so a session is bound. The problem is that all this happens very early in the creation of a Component when it's not fully initialized yet. If RPL implemented IComponentInitializationListener instead this problem wouldn't occur.
I can't really tell if it's a bug or not that adding a Behavior in an IComponentInstantiationListener makes pages stateful... Maybe that's just generally not a good idea.
--
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
[jira] [Resolved] (WICKET-4763) Page's stateless hint is initially
set to 'false'
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4763.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.1.0
Assignee: Martin Grigorov
Pages by default should be stateless. From now on Component#FLAG_RESERVED5 (Page#STATELESS_HINT) is set to 'true' by default.
> Page's stateless hint is initially set to 'false'
> -------------------------------------------------
>
> Key: WICKET-4763
> URL: https://issues.apache.org/jira/browse/WICKET-4763
> Project: Wicket
> Issue Type: Bug
> Components: wicket-devutils
> Affects Versions: 6.0.0
> Reporter: Christoph Leiter
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 6.1.0
>
>
> If RenderPerformanceListener is active then sessions will be created even for stateless pages. This happens because RPL is an IComponentInstantiationListener which adds a Behavior to every component. That causes a call to addStateChange() which in turns calls AbstractPageManager#touchPage. At this point #isPageStateless always returns false (!) and so a session is bound. The problem is that all this happens very early in the creation of a Component when it's not fully initialized yet. If RPL implemented IComponentInitializationListener instead this problem wouldn't occur.
> I can't really tell if it's a bug or not that adding a Behavior in an IComponentInstantiationListener makes pages stateful... Maybe that's just generally not a good idea.
--
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
[jira] [Updated] (WICKET-4763) Page's stateless hint is initially
set to 'false'
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-4763:
------------------------------------
Summary: Page's stateless hint is initially set to 'false' (was: RenderPerformanceListener causes session creation)
> Page's stateless hint is initially set to 'false'
> -------------------------------------------------
>
> Key: WICKET-4763
> URL: https://issues.apache.org/jira/browse/WICKET-4763
> Project: Wicket
> Issue Type: Bug
> Components: wicket-devutils
> Affects Versions: 6.0.0
> Reporter: Christoph Leiter
> Priority: Minor
>
> If RenderPerformanceListener is active then sessions will be created even for stateless pages. This happens because RPL is an IComponentInstantiationListener which adds a Behavior to every component. That causes a call to addStateChange() which in turns calls AbstractPageManager#touchPage. At this point #isPageStateless always returns false (!) and so a session is bound. The problem is that all this happens very early in the creation of a Component when it's not fully initialized yet. If RPL implemented IComponentInitializationListener instead this problem wouldn't occur.
> I can't really tell if it's a bug or not that adding a Behavior in an IComponentInstantiationListener makes pages stateful... Maybe that's just generally not a good idea.
--
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
[jira] [Updated] (WICKET-4763) Page's stateless hint is initially
set to 'false'
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-4763:
------------------------------------
Fix Version/s: 1.5.9
> Page's stateless hint is initially set to 'false'
> -------------------------------------------------
>
> Key: WICKET-4763
> URL: https://issues.apache.org/jira/browse/WICKET-4763
> Project: Wicket
> Issue Type: Bug
> Components: wicket-devutils
> Affects Versions: 6.0.0
> Reporter: Christoph Leiter
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 6.1.0, 1.5.9
>
>
> If RenderPerformanceListener is active then sessions will be created even for stateless pages. This happens because RPL is an IComponentInstantiationListener which adds a Behavior to every component. That causes a call to addStateChange() which in turns calls AbstractPageManager#touchPage. At this point #isPageStateless always returns false (!) and so a session is bound. The problem is that all this happens very early in the creation of a Component when it's not fully initialized yet. If RPL implemented IComponentInitializationListener instead this problem wouldn't occur.
> I can't really tell if it's a bug or not that adding a Behavior in an IComponentInstantiationListener makes pages stateful... Maybe that's just generally not a good idea.
--
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