[WICKET-6523] Two AbstractAjaxTimerBehaviors on same component timeId conflict

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 7.9.0, 8.0.0-M8
• Fix Version/s: 8.0.0-M9
• Component/s: wicket
• Assignee: Sven Meier
• Reporter: Sven Meier
• Created: 23/Jan/18 14:05
• Updated: 06/Feb/18 17:39
• Resolved: 06/Feb/18 17:38

Description

When two or more AbstractAjaxTimerBehaviors are added two the same component, they use an identical timerId (= markupId).

This can lead a stopping behavior erroneously stopping the other behavior instead of itself.

Issue Links

• relates to: WICKET-5570 Rescheduling the same ajax timer behavior causes memory leak in the browser
• relates to: WICKET-6191 AjaxTimerBehavior will stop after ajax update of component it is attached to
• relates to: WICKET-4959 Notify behaviors when a component is removed from the tree
• relates to: WICKET-4689 Javascript timers not removed when a Component is replaced by ajax
• links to: GitHub Pull Request #260