[
https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411577#comment-13411577
]
Steve Lowery commented on WICKET-4652:
--------------------------------------
Are you saying you believe this is fixed in the master line? This same code
appears in 6.0.0-beta2 as well.
> AbstractAjaxTimerBehavior throws ComponentNotFoundException when its
> component is replaced in PageMap.
> ------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4652
> URL: https://issues.apache.org/jira/browse/WICKET-4652
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.0.0-beta2
> Environment: Windows 7 with Jetty
> Reporter: Steve Lowery
> Priority: Minor
> Attachments: Wicket 1.5 Ajax Debug Window.jpg, timer15.war, timer6.war
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
