Akka base Exception.
Akka base Exception.
This exception is thrown when Akka detects a problem with the provided configuration
Typically used together with Future
to signal completion
but there is no actual value completed.
Typically used together with Future
to signal completion
but there is no actual value completed. More clearly signals intent
than Unit
and is available both from Scala and Java (which Unit
is not).
This type is used in generic type signatures wherever the actual value is of no importance.
This type is used in generic type signatures wherever the actual value is of no importance.
It is a combination of Scala’s Unit
and Java’s Void
, which both have different issues when
used from the other language. An example use-case is the materialized value of an Akka Stream for cases
where no result shall be returned from materialization.
Mix in this trait to suppress the StackTrace for the instance of the exception but not the cause, scala.util.control.NoStackTrace suppresses all the StackTraces.
Main class to start an akka.actor.ActorSystem with one top level application supervisor actor.
Main class to start an akka.actor.ActorSystem with one top level application supervisor actor. It will shutdown the actor system when the top level actor is terminated.
This package is used as a collection point for usage patterns which involve actors, futures, etc.
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:
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);