Narrow the type of this Behavior, which is always a safe operation.
Narrow the type of this Behavior, which is always a safe operation. This method is necessary to implement the contravariant nature of Behavior (which cannot be expressed directly due to type inference problems).
Process an incoming message and return the next behavior.
Process an incoming message and return the next behavior.
The returned behavior can in addition to normal behaviors be one of the canned special objects:
* returning stopped
will terminate this Behavior
* returning same
designates to reuse the current Behavior
* returning unhandled
keeps the same Behavior and signals that the message was not yet handled
Code calling this method should use Behavior$ canonicalize
to replace
the special objects with real Behaviors.
Process an incoming Signal and return the next behavior.
Process an incoming Signal and return the next behavior. This means that all lifecycle hooks, ReceiveTimeout, Terminated and Failed messages can initiate a behavior change.
The returned behavior can in addition to normal behaviors be one of the canned special objects:
* returning stopped
will terminate this Behavior
* returning same
designates to reuse the current Behavior
* returning unhandled
keeps the same Behavior and signals that the message was not yet handled
Code calling this method should use Behavior$ canonicalize
to replace
the special objects with real Behaviors.
Mutable behavior can be implemented by extending this class and implement the abstract method MutableBehavior#onMessage and optionally override MutableBehavior#onSignal.
Instances of this behavior should be created via Actor#mutable and if the ActorContext is needed it can be passed as a constructor parameter from the factory function.
Actor#mutable