Package org.apache.pekko.persistence.typed.javadsl

Class EffectBuilder<Event,State>

java.lang.Object
org.apache.pekko.persistence.typed.javadsl.EffectBuilder<Event,State>
All Implemented Interfaces:
Effect<Event,State>
Direct Known Subclasses:
PersistNothing$, Stash$, Unhandled$
public abstract class EffectBuilder<Event,State> extends Object implements Effect<Event,State>
A command handler returns an Effect directive that defines what event or events to persist.

Additional side effects can be performed in the callback thenRun

Instances of Effect are available through factories EventSourcedBehavior.Effect.

Not intended for user extension.

  • Constructor Details

    • EffectBuilder

      public EffectBuilder()

  • Method Details

    • thenNoReply

      public abstract ReplyEffect<Event,State> thenNoReply()
      When EventSourcedBehaviorWithEnforcedReplies 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.

    • thenReply

      public <ReplyMessage> ReplyEffect<Event,State> thenReply(ActorRef<ReplyMessage> replyTo, Function<State,ReplyMessage> replyWithMessage)
      Send a reply message to the command. The type of the reply message must conform to the type specified by the passed replyTo ActorRef.

      This has the same semantics as replyTo.tell.

      It is provided as a convenience (reducing boilerplate) and a way to enforce that replies are not forgotten when the EventSourcedBehavior is created with EventSourcedBehaviorWithEnforcedReplies. 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.

    • thenRun

      public final <NewState extends State> EffectBuilder<Event,State> thenRun(Procedure<NewState> callback)
      Run the given callback. Callbacks are run sequentially.

    • thenRun

      public final EffectBuilder<Event,State> thenRun(Effect callback)
      Run the given callback. Callbacks are run sequentially.

    • thenStop

      public abstract EffectBuilder<Event,State> thenStop()
      The side effect is to stop the actor

    • thenUnstashAll

      public abstract Effect<Event,State> thenUnstashAll()
      Unstash the commands that were stashed with EffectFactories.stash.

      It's allowed to stash messages while unstashing. Those newly added commands will not be processed by this unstashAll effect and have to be unstashed by another unstashAll.