camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicola Ferraro (JIRA)" <>
Subject [jira] [Commented] (CAMEL-10612) camel-reactive-streams - New component
Date Mon, 06 Feb 2017 10:37:41 GMT


Nicola Ferraro commented on CAMEL-10612:

Hi, I think we are almost done with this. I've also added examples and documentation, and
also a client API that can use Camel endpoints directly. I've added in-only and in-out communication
(both ways). For the auto-conversion during bean call (question above), I left it to be manually
specified by the user for now (there's an example).

The API has changed since the beginning of this issue, but I think now it's more consistent.

Users can define complex streams in Camel and pass them to the reactive framework, or just
use URIs:
// send the content of all files in "inbox" to a http URL
Flux.from(camel.from("file:inbox", String.class)) // Reactor Core 3
  .flatMap(file ->"http://theurl/hello"))
  // continue

The "from" and "to" methods create camel routes that use the reactive-streams component under
the hood. They have a "fromStream" (was "getPublisher") and "toStream" counterpart that allow
defining more complex routes in the Camel DSL side (they also allow to have fine grained control
over eg. backpressure).

I've also defined some rest services using the client API only (see examples).

[~davsclaus] and [~lb], if you have time, can you give me the last feedback?

> camel-reactive-streams - New component
> --------------------------------------
>                 Key: CAMEL-10612
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Nicola Ferraro
>            Assignee: Nicola Ferraro
>             Fix For: 2.19.0
> 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

View raw message