[WICKET-4652] AbstractAjaxTimerBehavior throws ComponentNotFoundException when its component is replaced in PageMap.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.0.0-beta2
• Fix Version/s: 6.0.0
• Component/s: wicket
• Environment: Windows 7 with Jetty
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Steve Lowery
• Created: 10/Jul/12 19:58
• Updated: 23/Jul/12 08:45
• Resolved: 23/Jul/12 08:45

Description

If a component with an AbstractAjaxTimerBehavior (or AjaxSelfUpdatingTimerBehavior) or any of its parents are replaced in the PageMap with another component, the next time behavior fires, you get a ComponentNotFoundException because the component with the attached behavior is no longer there.

Not sure what js magic made this work in previous versions of wicket, but it wasn't an issue in 1.4. Not sure about 1.5 as we are upgrading from 1.4 to 6.0.