MaybeObserver (RxJava Javadoc 3.1.10) (original) (raw)

Provides a mechanism for receiving push-based notification of a single value, an error or completion without any value.

When a MaybeObserver is subscribed to a MaybeSource through the MaybeSource.subscribe(MaybeObserver) method, the MaybeSource calls onSubscribe(Disposable) with a Disposable that allows disposing the sequence at any time. A well-behavedMaybeSource will call a MaybeObserver's onSuccess(Object), onError(Throwable) or onComplete() method exactly once as they are considered mutually exclusive terminal signals.

Calling the MaybeObserver's method must happen in a serialized fashion, that is, they must not be invoked concurrently by multiple threads in an overlapping fashion and the invocation pattern must adhere to the following protocol:

    onSubscribe (onSuccess | onError | onComplete)?

Note that unlike with the Observable protocol, onComplete() is not called after the success item has been signalled via onSuccess(Object).

Subscribing a MaybeObserver to multiple MaybeSources is not recommended. If such reuse happens, it is the duty of the MaybeObserver implementation to be ready to receive multiple calls to its methods and ensure proper concurrent behavior of its business logic.

Calling onSubscribe(Disposable), onSuccess(Object) or onError(Throwable) with anull argument is forbidden.

The implementations of the onXXX methods should avoid throwing runtime exceptions other than the following cases:

• If the argument is null, the methods can throw a NullPointerException. Note though that RxJava prevents nulls to enter into the flow and thus there is generally no need to check for nulls in flows assembled from standard sources and intermediate operators.
• If there is a fatal error (such as VirtualMachineError).