Hi all,
I’m trying to do something relatively simple, yet it’s been eluding me for
hours already!
I’d like to have a timer trigger a broadcast to a couple pipelines to invoke a
remote cloud component, transform the responses to a common type and merge the
results in one homogenous list to furt
a").pipeline("direct:x", "direct:y", "direct:z",
> "mock:result");
>
> On Thu, Oct 27, 2016 at 7:03 AM, Edoardo Causarano <
> edoardo.causar...@gmail.com> wrote:
>
>> Hi all,
>>
>> I’m trying to do something relativ
Hi Quinn,
Thanks that's correct, but really I was looking for a way to test the
construct timer+broadcast+pipelines+merged_processor.
Shoving the datasets to fake the remotes inside the pipelines made sense.
Anyway, I'll see if I have time to get back to this setup sometime later.
Right now I'm
Hi all,
I had some trouble figuring out how to multicast to some pipelines. I
eventually found a [working] definition, but I also expected other forms to
work such as:
.multicast().aggregationStrategy(AggregationStrategies.groupedExchange())
.pipeline("A", "B")
.pipeline("C", "D")
.end(
Hi Darius, that's correct, I'm expecting the START message to enter the
pipelines from their heads.
On Fri, 28 Oct 2016 at 20:43, DariusX wrote:
> It isn't clear what you want as the expected output.
> From your example, it seems that you have two "pipelines" and you want to
> multicast to send
Hi Brad,
yes that's the definition of multicast but the documentation also suggests
that pipelines are supposed to be implicitly derived from a vararg to(...)
statement.
In any case I don't understand how the multicast could leak into a vararg
pipeline(...). It really feels like a bug to me, but
Hi all,
these are the results I get, only the most explicit and verbose configuration
returns the expected result.
Working route:
.pipeline().to("A").to("B").end()
.pipeline().to("C").to("D").end()
10:41:12.644 [main] INFO route1 - after direct:start body=START
10:41:12.666 [main] DEBUG org.a
t the first
> elements in the multicast are like a pub/sub or JMS topic where each of the
> subscribers receive exactly the same message.
>
> On Tue, Nov 1, 2016 at 4:49 AM, Edoardo Causarano <
> edoardo.causar...@gmail.com> wrote:
>
>> Hi all,
>>
>> these a
HI,
I created a jira (CAMEL-10442) for this in case it’s a bug. Thanks for your
help.
Best,
Edoado
> On 1 Nov 2016, at 19:30, Brad Johnson wrote:
>
> Edoardo,
>
> I missed the second set of logging statements, sorry. I thought you'd said
> they were outputting the same thing. And, yes, t
Hi all,
just moved code from dev to testing and found that in real-life the DropBox
component blows apart in OOMs. Seems that it’s using plain BAOS (sic) to buffer
remote data which is not a particularly good idea when you have no idea how big
the files will be (or you’re pretty certain they’re
t;
> We love contributions, so you are very welcome to look into this and
> provide a PR / patch. And to log a JIRA ticket.
> http://camel.apache.org/contributing
>
> On Thu, Nov 10, 2016 at 11:50 AM, Edoardo Causarano
> wrote:
> > Hi all,
> >
> > just moved co
11 matches
Mail list logo
