Run the given callback after the current Effect
When PersistentBehaviorWithEnforcedReplies is used there will be compilation errors if the returned effect isn't a ReplyEffect.
When PersistentBehaviorWithEnforcedReplies is used there will be compilation errors if the returned effect
isn't a ReplyEffect. This thenNoReply
can be used as a conscious decision that a reply shouldn't be
sent for a specific command or the reply will be sent later.
The side effect is to stop the actor
Send a reply message to the command, which implements ExpectingReply.
Send a reply message to the command, which implements ExpectingReply. The type of the
reply message must conform to the type specified in ExpectingReply.replyTo ActorRef
.
This has the same semantics as cmd.replyTo().tell
.
It is provided as a convenience (reducing boilerplate) and a way to enforce that replies are not forgotten
when the PersistentBehavior
is created with PersistentBehaviorWithEnforcedReplies. When
withEnforcedReplies
is used there will be compilation errors if the returned effect isn't a ReplyEffect.
The reply message will be sent also if withEnforcedReplies
isn't used, but then the compiler will not help
finding mistakes.
Run the given callback.
Run the given callback. Callbacks are run sequentially.
Run the given callback.
Run the given callback. Callbacks are run sequentially.
A command handler returns an
Effect
directive that defines what event or events to persist.Additional side effects can be performed in the callback
andThen
Instances of
Effect
are available through factories PersistentBehavior.Effect.Not intended for user extension.