camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Sicker <boa...@gmail.com>
Subject Re: Why does RouteDefinition have "from" methods?
Date Sat, 13 Sep 2014 02:34:28 GMT
I think it's the other way around. You can make a bunch of
from(foo).to(bar), then do a from(bar) to get the combined channel.


On 12 September 2014 10:29, toomanyedwards <toomanyedwards@gmail.com> wrote:

> I understand that a route can have multiple inputs that lead to the same
> processing something like:
>    routeBuilder.from("direct:foo, direct:bar").to("direct:doSomething");
>
> But in the case I described earlier:
>    myRouteDefinition = routeBuilder.from("direct:foo");
>    myRouteDefinition.to("direct:doSomething");
>
>    myRouteDefinition.from("direct:buzz");
>    myRouteDefinition.to("direct:doSomethingElse");
>
> isn't this almost effectively two distinct routes vs multiple inputs into
> the same route?
>
> -e
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Why-does-RouteDefinition-have-from-methods-tp5756370p5756426.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Matt Sicker <boards@gmail.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message