Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop own Converters and use ReactiveAdapterRegistry directly where possible [DATACMNS-949] #1393

Closed
spring-projects-issues opened this issue Dec 4, 2016 · 1 comment
Assignees
Labels
in: repository type: task

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Dec 4, 2016

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 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.


Affects: 2.0 M1 (Kay)

Issue Links:

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Nov 14, 2019

Mark Paluch commented

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: repository type: task
Projects
None yet
Development

No branches or pull requests

2 participants