[
https://issues.apache.org/jira/browse/WICKET-5905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sven Meier updated WICKET-5905:
-------------------------------
Component/s: wicket
Affects Version/s: 7.0.0-M5
6.19.0
Martin suggested '/ajax/call/start', but I'd prefer 'init' (== constructor) to
prevent any ambiguity on when the event is triggered.
Any other suggestions?
> allow listening to Ajax calls before scheduling
> -----------------------------------------------
>
> Key: WICKET-5905
> URL: https://issues.apache.org/jira/browse/WICKET-5905
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 7.0.0-M5, 6.19.0
> Reporter: Sven Meier
> Assignee: Sven Meier
> Priority: Minor
>
> I need to execute custom JavaScript on each Ajax call, immediately after the
> event occurred. Topic "/ajax/call/before" is not suitable for this - if the
> call gets scheduled, the JavaScript is executed too late.
> I propose to add a new topic '/ajax/call/init', which is triggered just after
> creation of the Call, but before throttling and scheduling.
> See
> http://apache-wicket.1842946.n4.nabble.com/additional-global-ajax-listener-td4670715.html
> for discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
