Guten Tag Sven Meier, am Dienstag, 1. Oktober 2019 um 20:53 schrieben Sie: > Actually you could argue whether it is practical that these events > are not delivered to invisible or disabled components by default - > something I wouldn't expect, since it requires to override > #canCallListener() or a clever solution like yours.
+1, I was suprised as well in the past. AnnotationEventDispatcher is some kind of opt-in in the end already, so one can argue it should not care if to publish events or not at all. If receivers of events want to ignore some based on aspects like visibility of a component, if it's enabled or not etc., they could check that in the event handler on their own. Would have the benefit of being able to check that for each and every individual event (handler) as well. > IMHO we should make this configurable[...] Such a configuration has been explicitly removed in the past in favour of calling "canCallListener": https://github.com/wicketstuff/core/commit/f2ee61fb48259f9bdbf682713b12738e596d3cc1#diff-e8dc60d585cc63b237e8bb83a2814c3b https://github.com/wicketstuff/core/commit/f2ee61fb48259f9bdbf682713b12738e596d3cc1#diff-e1aa43fd3aadd18631700c7dd4c63179 So it might be worth it to consider re-introducing that configuration again, but with a changed default of "true" to send to invisible components. 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
