With #256 we introduced some configurable "event listener mapping" that allows to hook into the process of DomainEventInterface => EventListenerInterface resolution.
The expected listener method name is still hard coded to when<EventShortClass> in the EventListenerInvoker though.
The listener method invocation should be extracted to a configurable strategy so that this behavior is extensible. This is especially useful for standalone usage (#180) and might pave the way for "catch all event listeners" (#259).
With #256 we introduced some configurable "event listener mapping" that allows to hook into the process of
DomainEventInterface=>EventListenerInterfaceresolution.The expected listener method name is still hard coded to
when<EventShortClass>in the EventListenerInvoker though.The listener method invocation should be extracted to a configurable strategy so that this behavior is extensible. This is especially useful for standalone usage (#180) and might pave the way for "catch all event listeners" (#259).