Packages

  • package root
    Definition Classes
    root
  • package akka
    Definition Classes
    root
  • package pattern

    This package is used as a collection point for usage patterns which involve actors, futures, etc.

    Commonly Used Patterns With Akka

    This package is used as a collection point for usage patterns which involve actors, futures, etc. but are loosely enough coupled to (multiple of) them to present them separately from the core implementation. Currently supported are:

    • ask: create a temporary one-off actor for receiving a reply to a message and complete a scala.concurrent.Future with it; returns said Future.
    • pipeTo: feed eventually computed value of a future to an akka.actor.ActorRef as a message.
    • pipeToSelection: feed eventually computed value of a future to an akka.actor.ActorSelection as a message.

    In Scala the recommended usage is to import the pattern from the package object:

    import akka.pattern.ask
    
    ask(actor, message) // use it directly
    actor ask message   // use it by implicit conversion

    For Java the patterns are available as static methods of the akka.pattern.Patterns class:

    import static akka.pattern.Patterns.ask;
    
    ask(actor, message);
    Definition Classes
    akka
  • object StatusReply
    Definition Classes
    pattern
  • Error
  • ErrorMessage
  • Success

object Error

Scala API for creating and pattern matching an error response

For example: case StatusReply.Error(exception) => ...

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

Value Members

  1. def apply[T](exception: Throwable): StatusReply[T]

    Scala API: Create an error response with a user defined Throwable.

    Scala API: Create an error response with a user defined Throwable.

    Prefer the string based error response over this one when possible to avoid tightly coupled logic across actors and passing internal failure details on to callers that can not do much to handle them.

    For cases where types are needed to identify errors and behave differently enumerating them with a specific set of response messages may be a better alternative to encoding them as generic exceptions.

    Also note that Akka does not contain pre-build serializers for arbitrary exceptions.

  2. def apply[T](errorMessage: String): StatusReply[T]

    Scala API: Create an status response with a error message describing why the request was failed or denied.

  3. def unapply(status: StatusReply[_]): Option[Throwable]