Composition adapters for Reactive Streams [SPR-14159]

[spring-projects-issues]

Rossen Stoyanchev opened SPR-14159 and commented

Add a GenericConverter for adapting async types (RxJava 1.x and CompletableFuture) to Reactive Streams using Project Reactor converters to Flux and Mono. This makes it easy to work with any composition library within the framework and also to check stream semantics (stream of 0..1 vs stream of many).

---

Affects: 4.2.5

Reference URL: https://github.com/spring-projects/spring-reactive/tree/master/src/main/java/org/springframework/core/convert/support

Issue Links:

• Support for RxJava 2 [SPR-14628] #19195 Support for RxJava 2

Referenced from: commits 101220b

[spring-projects-issues]

Mark Paluch commented

I think it would make also sense to be able to convert between Project Reactor/Reactive Streams and RxJava types.

[spring-projects-issues]

Juergen Hoeller commented

I'm not sure whether this should really live within the converter abstraction, triggered by ConversionService use. As discussed in our Reactor 3.0 review sessions, converters to me are about producing independent value objects of a different type, not about adapting to wrapper types with "hot" references back to the original object.

Even the existing ReactorToRxJava1Converter and MonoToCompletableFutureConverter in master are an issue here. I'd rather have explicit RxJava1Adapter and Mono.from calls in places where they are actually needed, e.g. in the spring-web-reactive module, possibly behind an adapter registration mechanism that would again live in the core module. Either way, it would also avoid the significant overhead that comes with ConversionService use.