StatusReply$

java.lang.Object

org.apache.pekko.pattern.StatusReply$

public class StatusReply$ extends Object

Field Summary

Fields

Modifier and Type

Field

Description

static final StatusReply$

MODULE$

Static reference to the singleton instance of this Scala object.
Constructor Summary

Constructors

Constructor

Description

StatusReply$()
Method Summary

Modifier and Type

Method

Description

StatusReply<Done>

ack()

Java API: A general purpose message for using as an Ack

StatusReply<Done>

Ack()

Scala API: A general purpose message for using as an Ack

<T> StatusReply<T>

error(String errorMessage)

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

<T> StatusReply<T>

error(Throwable exception)

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

<T> StatusReply<T>

success(T value)

Java API: Create a successful reply containing value

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Details
- MODULE$
  
  public static final StatusReply$ MODULE$
  
  Static reference to the singleton instance of this Scala object.
Constructor Details
- StatusReply$
  
  public StatusReply$()
Method Details
- Ack
  
  public StatusReply<Done> Ack()
  
  Scala API: A general purpose message for using as an Ack
- ack
  
  public StatusReply<Done> ack()
  
  Java API: A general purpose message for using as an Ack
- success
  
  public <T> StatusReply<T> success(T value)
  
  Java API: Create a successful reply containing value
- error
  
  public <T> StatusReply<T> error(String errorMessage)
  
  Java API: Create an status response with a error message describing why the request was failed or denied.
- error
  
  public <T> StatusReply<T> error(Throwable exception)
  
  Java 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 Pekko does not contain pre-build serializers for arbitrary exceptions.