You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Steve Lowery (JIRA)" <ji...@apache.org> on 2012/07/10 21:58:34 UTC
[jira] [Created] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Steve Lowery created WICKET-4652:
------------------------------------
Summary: 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
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
[jira] [Commented] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411579#comment-13411579 ]
Martin Grigorov commented on WICKET-4652:
-----------------------------------------
No, this code is there since the rewrite of the Ajax code. For some reason it doesn't work for your case.
Please attach a proper quickstart app. Deploying .war and injecting fixes in it is very time consuming.
> 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
[jira] [Resolved] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4652.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.0.0
Fixed.
It was a problem in Wicket.DOM.inDoc() method.
> 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
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 6.0.0
>
> Attachments: Wicket 1.5 Ajax Debug Window.jpg, timer-quickstart.zip, 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
[jira] [Updated] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Steve Lowery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lowery updated WICKET-4652:
---------------------------------
Attachment: (was: TimerQuickStart.zip)
> 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
[jira] [Assigned] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reassigned WICKET-4652:
---------------------------------------
Assignee: Martin Grigorov
> 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
> Assignee: Martin Grigorov
> Priority: Minor
> Attachments: Wicket 1.5 Ajax Debug Window.jpg, timer-quickstart.zip, 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
[jira] [Commented] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411571#comment-13411571 ]
Martin Grigorov commented on WICKET-4652:
-----------------------------------------
There is default precondition at wicket-ajax-jquery.js, line 442 (latest code in master):
// the precondition to use if there are no explicit ones
defaultPrecondition = [ function () {
if (attrs.c) {
if (attrs.f) {
return Wicket.$$(attrs.c) && Wicket.$$(attrs.f);
} else {
return Wicket.$$(attrs.c);
}
}
}];
i.e. it checks whether the component is in the document.
> 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
[jira] [Updated] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Steve Lowery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lowery updated WICKET-4652:
---------------------------------
Attachment: Wicket 1.5 Ajax Debug Window.jpg
Notice last line stating "Ajax GET stopped because of precondition..."
> 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
[jira] [Updated] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Steve Lowery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lowery updated WICKET-4652:
---------------------------------
Attachment: timer15.war
timer6.war
> 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
[jira] [Resolved] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-4652.
-------------------------------------
Resolution: Not A Problem
> 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: TimerQuickStart.zip
>
>
> 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
[jira] [Updated] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Steve Lowery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lowery updated WICKET-4652:
---------------------------------
Attachment: TimerQuickStart.zip
This java and html will show the described behavior
> 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: TimerQuickStart.zip
>
>
> 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
[jira] [Commented] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411288#comment-13411288 ]
Martin Grigorov commented on WICKET-4652:
-----------------------------------------
I'm not sure either how this worked for you in 1.4...
In 6.0 the timer behavior has an additional logic to clear the timer (JS: clearTimeout()) when it is stopped. Your code doesn't stop it, so I think it it a problem in your code.
This is like not closing DB resources (connections, statements), Wicket cannot help you in cases like this.
If you debug what made it working in 1.4 and prove that there is a regression in 6.0 then I'll reopen the ticket. Otherwise I recommend you to stop the timer behavior when you replace the connected component (see org.apache.wicket.ajax.AbstractAjaxTimerBehavior#stop(AjaxRequestTarget)).
> 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: TimerQuickStart.zip
>
>
> 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
[jira] [Commented] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Steve Lowery (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Reopened] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov reopened WICKET-4652:
-------------------------------------
> 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
[jira] [Commented] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Steve Lowery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411566#comment-13411566 ]
Steve Lowery commented on WICKET-4652:
--------------------------------------
This is a regression in wicket 6. Works fine in the 1.4 and 1.5 lines. If I can read the javascript correctly, it looks like wicketAjaxGet/Post take in a precondition. In wicket 1.5, the precondition is function() {var c = Wicket.$(\'myid\'); return typeof(c) != \'undefined\' && c != null}.bind(this), which is checking that the component is still on the page. Looks like 6.0 is not providing a precondition, so it calls the url and fails when it attempts to update the component which is no longer on the page.
I will attach an app with wicket 6.0 and wicket 1.5 and you can see it works in 1.5, but not 6.0.
> 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: TimerQuickStart.zip
>
>
> 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
[jira] [Updated] (WICKET-4652) AbstractAjaxTimerBehavior throws
ComponentNotFoundException when its component is replaced in PageMap.
Posted by "Steve Lowery (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Lowery updated WICKET-4652:
---------------------------------
Attachment: timer-quickstart.zip
This is the first quickstart I've created. If something is missing, or you need more, let me know. The JUnit doesn't fail, but you can plainly see it fail in the browser.
> 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, timer-quickstart.zip, 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