You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Robert Dahlström (JIRA)" <ji...@apache.org> on 2010/01/05 14:38:54 UTC
[jira] Created: (WICKET-2660) Wickettester executeAllTimerBehaviors
executes stopped behaviors too
Wickettester executeAllTimerBehaviors executes stopped behaviors too
--------------------------------------------------------------------
Key: WICKET-2660
URL: https://issues.apache.org/jira/browse/WICKET-2660
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.4.5
Reporter: Robert Dahlström
When attempting to test a page with two ajax timer behaviours the first behaviour is triggered correctly. Then that behaviour is stopped (using the stop function) and a second behaviour is started. If executeAllTimerBehaviors is called again both behaviours are triggered even though one is stopped.
It would be good if the code in BaseWicketTester.executeAllTimerBehaviors(MarkupContainer container) could validate if the behaviour is stopped or not before trying to execute it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-2660) Wickettester
executeAllTimerBehaviors executes stopped behaviors too
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2660.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M1
1.4.7
Assignee: Igor Vaynberg
> Wickettester executeAllTimerBehaviors executes stopped behaviors too
> --------------------------------------------------------------------
>
> Key: WICKET-2660
> URL: https://issues.apache.org/jira/browse/WICKET-2660
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.5
> Reporter: Robert Dahlström
> Assignee: Igor Vaynberg
> Fix For: 1.4.7, 1.5-M1
>
> Attachments: WICKET-2660.patch
>
>
> When attempting to test a page with two ajax timer behaviours the first behaviour is triggered correctly. Then that behaviour is stopped (using the stop function) and a second behaviour is started. If executeAllTimerBehaviors is called again both behaviours are triggered even though one is stopped.
> It would be good if the code in BaseWicketTester.executeAllTimerBehaviors(MarkupContainer container) could validate if the behaviour is stopped or not before trying to execute it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-2660) Wickettester executeAllTimerBehaviors
executes stopped behaviors too
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov updated WICKET-2660:
------------------------------------
Attachment: WICKET-2660.patch
> Wickettester executeAllTimerBehaviors executes stopped behaviors too
> --------------------------------------------------------------------
>
> Key: WICKET-2660
> URL: https://issues.apache.org/jira/browse/WICKET-2660
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.5
> Reporter: Robert Dahlström
> Attachments: WICKET-2660.patch
>
>
> When attempting to test a page with two ajax timer behaviours the first behaviour is triggered correctly. Then that behaviour is stopped (using the stop function) and a second behaviour is started. If executeAllTimerBehaviors is called again both behaviours are triggered even though one is stopped.
> It would be good if the code in BaseWicketTester.executeAllTimerBehaviors(MarkupContainer container) could validate if the behaviour is stopped or not before trying to execute it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.