Handler Enhancers
Handler Enhancers allow you to wrap handlers and add custom logic to the execution, or eligibility of handlers for a certain message. This differs from HandlerInterceptor
s in that you have access to the aggregate member at the time of resolving, and it allows for more fine-grained control. You can use handler enhancers to intercept and perform checks on groups of @CommandHandler
s or @EventHandler
s.
To create a handler enhancer you start by implementing HandlerEnhancerDefinition
and overriding the wrapHandler()
method. All this method does is give you access to the MessageHandlingMember<T>
which is an object representing any handler that is specified in the system.
You can then sort these handlers based on their annotations by using the annotationAttributes(Annotation annotation)
method. This will filter out only those handlers that use that Annotation
.
For your handler enhancer to run you'll need to either create a META-INF/services/org.axonframework.messaging.annotation.HandlerEnhancerDefinition
file containing the fully qualified class name of the handler enhancer you have created, or register it explicitly in the Configurer.
Example of a Handler Enhancer that filters messages based on an expected Meta-Data key and value.
Implement the
HandlerEnhancerDefinition
interfaceOverride the
wrapHandler
method to perform your own logic.Sort out the types of handlers you want to wrap, for example any handlers with a
MyAnnotation
.Handle the method inside of a
MessageHandlingMember
, in this case, indicating the handler is only suitable if the meta-data key matches a value.If you are not interested in wrapping the handler, just return the original that was passed into the
wrapHandler
method.
It is possible to configure HandlerDefinition
with Axon Configuration
. If you are using Spring Boot defining HandlerDefintion
s and HandlerEnhancerDefinition
s as beans is sufficient (Axon autoconfiguration will pick them up and configure within Axon Configuration
).
Last updated