Interface Effect<Event,​State>

    • Method Detail

      • events

        scala.collection.immutable.Seq<Event> events()
      • thenRun

        Effect<Event,​State> thenRun​(scala.Function1<State,​scala.runtime.BoxedUnit> callback)
        Run the given callback. Callbacks are run sequentially.
        Parameters:
        callback - (undocumented)
        Returns:
        (undocumented)
      • andThen

        Effect<Event,​State> andThen​(SideEffect<State> chainedEffect)
        Run the given callback after the current Effect
        Parameters:
        chainedEffect - (undocumented)
        Returns:
        (undocumented)
      • andThen

        Effect<Event,​State> andThen​(scala.collection.immutable.Seq<SideEffect<State>> chainedEffects)
        Run the given callbacks sequentially after the current Effect
        Parameters:
        chainedEffects - (undocumented)
        Returns:
        (undocumented)
      • thenStop

        Effect<Event,​State> thenStop()
        The side effect is to stop the actor
      • thenUnstashAll

        Effect<Event,​State> thenUnstashAll()
        Unstash the commands that were stashed with Effect.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)
      • thenReply

        <ReplyMessage> ReplyEffect<Event,​State> thenReply​(ExpectingReply<ReplyMessage> cmd,
                                                                scala.Function1<State,​ReplyMessage> replyWithMessage)
        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 EventSourcedBehavior is created with EventSourcedBehavior.withEnforcedReplies. 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:
        cmd - (undocumented)
        replyWithMessage - (undocumented)
        Returns:
        (undocumented)
      • thenNoReply

        ReplyEffect<Event,​State> thenNoReply()
        When EventSourcedBehavior.withEnforcedReplies 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)