Deprecated API

Contents

• Deprecated Classes
• Deprecated Methods
• Deprecated Constructors

Deprecated Classes

Class and Description
reactor.core.publisher.DirectProcessor To be removed in 3.5, prefer clear cut usage of Sinks. Closest sink is Sinks.many().multicast().directBestEffort(), except it doesn't terminate overflowing downstreams.
reactor.core.publisher.EmitterProcessor To be removed in 3.5. Prefer clear cut usage of Sinks through variations of Sinks.many().multicast().onBackpressureBuffer(). This processor was blocking in EmitterProcessor.onNext(Object). This behaviour can be implemented with the Sinks API by calling Sinks.Many.tryEmitNext(Object) and retrying, e.g.: while (sink.tryEmitNext(v).hasFailed()) { LockSupport.parkNanos(10); }
reactor.core.publisher.FluxProcessor Processors will be removed in 3.5. Prefer using Sinks.Many instead, * or see https://github.com/reactor/reactor-core/issues/2431 for alternatives
reactor.core.publisher.MonoProcessor Processors will be removed in 3.5. Prefer using Sinks.One or Sinks.Empty instead, or see https://github.com/reactor/reactor-core/issues/2431 for alternatives
reactor.core.publisher.ReplayProcessor To be removed in 3.5, prefer clear cut usage of Sinks through variations under Sinks.many().replay().
reactor.core.publisher.UnicastProcessor to be removed in 3.5, prefer clear cut usage of Sinks through variations under Sinks.many().unicast().

Deprecated Methods

Method and Description
reactor.core.publisher.Hooks.addCallSiteInfo(P, String) Should only be used by the instrumentation, DOES NOT guarantee any compatibility
reactor.core.publisher.Hooks.addReturnInfo(P, String) Should only be used by the instrumentation, DOES NOT guarantee any compatibility
reactor.core.publisher.MonoProcessor.cancel() the MonoProcessor will cease to implement Subscription in 3.5
reactor.core.publisher.MonoProcessor.create() Use Sinks.one(), to be removed in 3.5
reactor.core.publisher.UnicastProcessor.create(Queue<E>, Consumer<? super E>, Disposable) should not expose onOverflow / remove in a future reactor version
reactor.core.publisher.Mono.deferWithContext(Function<Context, ? extends Mono<? extends T>>) use Mono.deferContextual(Function) instead. to be removed in 3.5.0.
reactor.core.publisher.Flux.deferWithContext(Function<Context, ? extends Publisher<T>>) use Flux.deferContextual(Function)
reactor.core.publisher.Mono.doAfterSuccessOrError(BiConsumer<? super T, Throwable>) prefer using Mono.doAfterTerminate(Runnable) or Mono.doFinally(Consumer). will be removed in 3.4.0
reactor.core.publisher.Mono.doOnSuccessOrError(BiConsumer<? super T, Throwable>) prefer using Mono.doOnNext(Consumer), Mono.doOnError(Consumer), Mono.doOnTerminate(Runnable) or Mono.doOnSuccess(Consumer). will be removed in 3.4.0
reactor.core.scheduler.Schedulers.elastic() use Schedulers.boundedElastic(), to be removed in 3.5.0
reactor.core.publisher.Mono.first(Iterable<? extends Mono<? extends T>>) use Mono.firstWithSignal(Iterable). To be removed in reactor 3.5.
reactor.core.publisher.Flux.first(Iterable<? extends Publisher<? extends I>>) use Flux.firstWithSignal(Iterable). To be removed in reactor 3.5.
reactor.core.publisher.Mono.first(Mono<? extends T>...) use Mono.firstWithSignal(Mono[]). To be removed in reactor 3.5.
reactor.core.publisher.Flux.first(Publisher<? extends I>...) use Flux.firstWithSignal(Publisher[]). To be removed in reactor 3.5.
reactor.core.publisher.Signal.getContext() use Signal.getContextView() instead. To be removed in 3.5.0
reactor.core.publisher.MonoProcessor.isCancelled() the MonoProcessor will cease to implement Subscription and this method will be removed in 3.5
reactor.core.scheduler.Schedulers.newElastic(int, ThreadFactory) use Schedulers.newBoundedElastic(int, int, ThreadFactory, int), to be removed in 3.5.0
reactor.core.scheduler.Schedulers.Factory.newElastic(int, ThreadFactory) use Schedulers.Factory.newBoundedElastic(int, int, ThreadFactory, int), to be removed in 3.5.0
reactor.core.scheduler.Schedulers.newElastic(String) use Schedulers.newBoundedElastic(int, int, String), to be removed in 3.5.0
reactor.core.scheduler.Schedulers.newElastic(String, int) use Schedulers.newBoundedElastic(int, int, String, int), to be removed in 3.5.0
reactor.core.scheduler.Schedulers.newElastic(String, int, boolean) use Schedulers.newBoundedElastic(int, int, String, int, boolean), to be removed in 3.5.0
reactor.core.publisher.MonoProcessor.peek() this method is discouraged, consider peeking into a MonoProcessor by turning it into a CompletableFuture
reactor.core.publisher.Flux.publishNext() use Flux.shareNext() instead, or use `publish().next()` if you need to `connect(). To be removed in 3.5.0
reactor.util.context.Context.putAll(Context) will be removed in 3.5, kept for backward compatibility with 3.3
reactor.core.publisher.MonoProcessor.request(long) the MonoProcessor will cease to implement Subscription in 3.5
reactor.core.publisher.FluxProcessor.sink() To be removed in 3.5, prefer clear cut usage of Sinks through the Sinks.many() spec.
reactor.core.publisher.FluxProcessor.sink(FluxSink.OverflowStrategy) To be removed in 3.5, prefer clear cut usage of Sinks through the Sinks.many() spec.
reactor.core.publisher.Flux.subscribe(Consumer<? super T>, Consumer<? super Throwable>, Runnable, Consumer<? super Subscription>) Because users tend to forget to request the subsciption. If the behavior is really needed, consider using Flux.subscribeWith(Subscriber). To be removed in 3.5.
reactor.core.publisher.Mono.subscriberContext() Use Mono.deferContextual(Function) or Mono.transformDeferredContextual(BiFunction) to materialize the context. To obtain the same Mono of Context, use Mono.deferContextual(Mono::just). To be removed in 3.5.0.
reactor.core.publisher.Flux.subscriberContext(Context) Use Flux.contextWrite(ContextView) instead. To be removed in 3.5.0.
reactor.core.publisher.Mono.subscriberContext(Context) Use Mono.contextWrite(ContextView) instead. To be removed in 3.5.0.
reactor.core.publisher.Flux.subscriberContext(Function<Context, Context>) Use Flux.contextWrite(Function) instead. To be removed in 3.5.0.
reactor.core.publisher.Mono.subscriberContext(Function<Context, Context>) Use Mono.contextWrite(Function) instead. To be removed in 3.5.0.
reactor.core.publisher.FluxProcessor.switchOnNext() should use Sinks, Sinks.Many.asFlux() and Flux.switchOnNext(Publisher). To be removed in 3.5.0.
reactor.core.publisher.Mono.toProcessor() prefer Mono.share() to share a parent subscription, or use Sinks

Deprecated Constructors

Constructor and Description
reactor.core.publisher.UnicastProcessor(Queue<T>, Consumer<? super T>, Disposable)