Guten Tag Thorsten Schöning,
am Dienstag, 1. Oktober 2019 um 16:15 schrieben Sie:
>> public boolean canCallListener(Method method)
>> {
>> if (method.isAnnotationPresent(OnEvent.class))
>> {
>> return true;
>> }
>>
>> return super.canCallListener(method);
>> }
> That callback doesn't exist anymore and I'm wondering how I'm able to
> recognize my custom event?[...]
That statement is misleading: I don't want to recognize my custom
event, but AnnotationEventDispatcher trying to send that to me
instead. AnnotationEventDispatcher gets all methods annotated using
"@OnEvent" and in Wicket 7 was checking if to dispatch an event to a
component using those methods.
> for (Method method : onEventMethods)
> {
> if (canCallListenerInterface(sink, method))
> {
That way I could be somewhat sure to only return "true" for my own
custom event. With removing the "Method"-argument I don't know how to
distinguish AnnotationEventDispatcher from everything else anymore.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
