Class EffectBuilder<Event,​State>

  • Type Parameters:
    NewState - The type of the state after the event is persisted, when not specified will be the same as State but if a known subtype of State is expected that can be specified instead (preferrably by explicitly typing the lambda parameter like so: thenRun((SubState state) -> { ... })). If the state is not of the expected type an ClassCastException is thrown.

    All Implemented Interfaces:
    Effect<Event,​State>
    Direct Known Subclasses:
    EffectImpl

    public abstract class EffectBuilder<Event,​State>
    extends java.lang.Object
    implements Effect<Event,​State>
    Run the given callback. Callbacks are run sequentially.

    • Constructor Detail

      • EffectBuilder

        public EffectBuilder()
    • Method Detail

      • 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.
        Returns:
        (undocumented)
      • 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.

        Parameters:
        replyTo - (undocumented)
        replyWithMessage - (undocumented)
        Returns:
        (undocumented)
      • thenRun

        public final EffectBuilder<Event,​State> thenRun​(Effect callback)
        Run the given callback. Callbacks are run sequentially.
        Parameters:
        callback - (undocumented)
        Returns:
        (undocumented)
      • 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.

        Returns:
        (undocumented)