[
https://issues.apache.org/jira/browse/WICKET-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100767#comment-16100767
]
ASF GitHub Bot commented on WICKET-6427:
----------------------------------------
Github user martin-g commented on a diff in the pull request:
https://github.com/apache/wicket/pull/223#discussion_r129422438
--- Diff:
wicket-core/src/main/java/org/apache/wicket/ajax/res/js/wicket-event-jquery.js
---
@@ -277,6 +277,10 @@
* @param topic {String} - the channel name for which
all subscribers will be notified.
*/
publish: function (topic) {
+ if (topic === Topic.AJAX_HANDLERS_BOUND) {
+ console.warn("As of Wicket 8,
Topic.AJAX_HANDLERS_BOUND has been deprecated in favour of
Topic.AJAX_ONDOMREADY_EVENTS_BOUND and will be removed in Wicket 9.")
+ topic = Topic.AJAX_ONDOMREADY_EVENTS_BOUND;
+ }
--- End diff --
To be backward compatible we will have to still publish this event together
with the new one.
This check and warning should be moved to `#subscribe()`.
> Fire an event once all ajax timers are registered
> -------------------------------------------------
>
> Key: WICKET-6427
> URL: https://issues.apache.org/jira/browse/WICKET-6427
> Project: Wicket
> Issue Type: Improvement
> Reporter: Jezza
> Priority: Minor
>
> This is in the same vein as WICKET-5746.
> I just need some way to execute code after the timers have been registered,
> and it seemed weird to only have the event fired for one set of ajax related
> calls.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
