Packages

object Effect

Factory methods for creating Effect directives - how a persistent actor reacts on a command.

Source
Effect.scala
Linear Supertypes
AnyRef, Any
Ordering
  1. Alphabetic
  2. By Inheritance
Inherited
  1. Effect
  2. AnyRef
  3. Any
  1. Hide All
  2. Show All
Visibility
  1. Public
  2. All

Value Members

  1. def noReply[Event, State]: ReplyEffect[Event, State]

    When EventSourcedBehavior.withEnforcedReplies is used there will be compilation errors if the returned effect isn't a ReplyEffect.

    When EventSourcedBehavior.withEnforcedReplies is used there will be compilation errors if the returned effect isn't a ReplyEffect. This noReply 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.

  2. def none[Event, State]: Effect[Event, State]

    Do not persist anything

    Do not persist anything

    Side effects can be chained with andThen

  3. def persist[Event, State](events: Seq[Event]): Effect[Event, State]

    Persist multiple events

    Persist multiple events

    Side effects can be chained with andThen

  4. def persist[Event, A <: Event, B <: Event, State](evt1: A, evt2: B, events: Event*): Effect[Event, State]

    Persist multiple events

    Persist multiple events

    Side effects can be chained with andThen

  5. def persist[Event, State](event: Event): Effect[Event, State]

    Persist a single event

    Persist a single event

    Side effects can be chained with andThen

  6. def reply[ReplyMessage, Event, State](cmd: ExpectingReply[ReplyMessage])(replyWithMessage: ReplyMessage): ReplyEffect[Event, State]

    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 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.

  7. def stash[Event, State](): ReplyEffect[Event, State]

    Stash the current command.

    Stash the current command. Can be unstashed later with Effect.unstashAll.

    Note that the stashed commands are kept in an in-memory buffer, so in case of a crash they will not be processed. They will also be discarded if the actor is restarted (or stopped) due to that an exception was thrown from processing a command or side effect after persisting. The stash buffer is preserved for persist failures if a backoff supervisor strategy is defined with EventSourcedBehavior.onPersistFailure.

    Side effects can be chained with andThen

  8. def stop[Event, State](): Effect[Event, State]

    Stop this persistent actor Side effects can be chained with andThen

  9. def unhandled[Event, State]: Effect[Event, State]

    This command is not handled, but it is not an error that it isn't.

    This command is not handled, but it is not an error that it isn't.

    Side effects can be chained with andThen

  10. def unstashAll[Event, State](): Effect[Event, State]

    Unstash the commands that were stashed with Effect.stash.

    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.

    Side effects can be chained with andThen, but note that the side effect is run immediately and not after processing all unstashed commands.

    See also

    Effect.thenUnstashAll