[
https://issues.apache.org/jira/browse/CAMEL-10612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842936#comment-15842936
]
Nicola Ferraro commented on CAMEL-10612:
----------------------------------------
What still needs to be done:
- allow automatic discovery of publishers and subscribers
- make the buffer strategy a.. strategy
- write proper documentation
- move some global options to the producer endpoint (need to find a way to do
it properly)
- add the possibility to handle "onError" and "onComplete" events in the Camel
route
- improve context shutdown by closing correctly all streams
- test with other frameworks (currently using rxjava2, reactive-streams TCK and
custom pub/sub)
- check osgi compliance
- add the ReactiveStreamService to the spring-boot application context in the
starter
- add bidirectional in-out communication from camel to the external lib (using
processors or similar)
> camel-reactive-streams - New component
> --------------------------------------
>
> Key: CAMEL-10612
> URL: https://issues.apache.org/jira/browse/CAMEL-10612
> Project: Camel
> Issue Type: New Feature
> Reporter: Nicola Ferraro
> Assignee: Nicola Ferraro
>
> We have a component for rx-java v1. rx-java v2 now is out and compatible with
> the reactive-stream specs, like many other reactive frameworks (including
> vert.x). We may want to implement a new component to integrate with any
> framework that comply with the reactive-streams specs (Akka-Streams and Slick
> among the others).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
