You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Constructor Command Handler has a number of limitations compared to regular Command Handler (instance) methods. These should be documented explicitly in the reference guide:
[ ] @ExceptionHandler annotated methods aren't invoked - since there is no instance to invoke a method on
[ ] @HandlerInterceptor annotated methods aren't invoked - since there is no instance to invoke a method on
[ ] AggregateLifecycle.apply() invocations will not result in an immediate invocation of the @EventSourcingHandler. Instead, the @EventSourcingHandler methods are invoked once the constructor completes.
Also, we should (gently) promote the use of instance method with @CreationPolicy(ALWAYS) as an alternative to Constructor Command Handlers.
The text was updated successfully, but these errors were encountered:
The Constructor Command Handler has a number of limitations compared to regular Command Handler (instance) methods. These should be documented explicitly in the reference guide:
[ ]
@ExceptionHandler
annotated methods aren't invoked - since there is no instance to invoke a method on[ ]
@HandlerInterceptor
annotated methods aren't invoked - since there is no instance to invoke a method on[ ]
AggregateLifecycle.apply()
invocations will not result in an immediate invocation of the@EventSourcingHandler
. Instead, the@EventSourcingHandler
methods are invoked once the constructor completes.Also, we should (gently) promote the use of instance method with
@CreationPolicy(ALWAYS)
as an alternative to Constructor Command Handlers.The text was updated successfully, but these errors were encountered: