Currently, we take an indirection via Converter for reactive type adoption that requires registration of own converters. Reactive types of the same multiplicity (Flux to Observable/Flowable or Single to Mono) could be adopted by using ReactiveAdapterRegistry directly. Using ReactiveAdapterRegistry without ConversionService introduces a dependency to Publisher which only matters if pure RxJava 1 is used - Project Reactor and RxJava 2 are based on Reactive Streams.
Will be handled in the context of DATACMNS-1508. We should reuse ReactiveAdapterRegistry if we can instead of being required to register new wrapper types
Mark Paluch opened DATACMNS-949 and commented
Currently, we take an indirection via
Converter
for reactive type adoption that requires registration of own converters. Reactive types of the same multiplicity (Flux
toObservable
/Flowable
orSingle
toMono
) could be adopted by usingReactiveAdapterRegistry
directly. UsingReactiveAdapterRegistry
withoutConversionService
introduces a dependency toPublisher
which only matters if pure RxJava 1 is used - Project Reactor and RxJava 2 are based on Reactive Streams.Affects: 2.0 M1 (Kay)
Issue Links:
DATACMNS-947 Adopt ReactiveTypeDescriptor changes
DATACMNS-1508 Add support for Coroutines repositories
The text was updated successfully, but these errors were encountered: