Hi,
I have done a migration of Camel and i use completionTimeOut for my
aggregates.
But i would prefer used CompletionSize, with a dynamic size which is
register with a split before.
from(TARIF_LISTE_SIMULATION).routeId(TARIF_LISTE_SIMULATION)
.bean(HeaderSetter.class
Than using both splitter + aggregator.
On Fri, Apr 20, 2012 at 11:01 AM, mathieuJ wrote:
> Hi,
>
> I have done a migration of Camel and i use completionTimeOut for my
> aggregates.
>
> But i would prefer used CompletionSize, with a dynamic size which is
> register wit
Hi
Motivated by Claus' nice words :-) and to take a whiff of the Camel code, I
analyzed my own Jira issue CAMEL-7146.
In the method "doAggregation" the aggregator evaluates if the aggregation
is complete. With completionSize = 1 this is the case on every Exchange.
Therefore the
Sorry, the message was sent too early...
The question to the Camel gurus is: what is more preferable:
1) On completionSize = 1 Camel throws an exception on context startup since
this is treated as "invalid configuration"
2) The aggregator should just check for the very speci
GitHub user vrlgohel opened a pull request:
https://github.com/apache/camel/pull/1844
[CAMEL-101276] Refactored completionSize & completionTimeout expressions
completionTimeout & completionSize attributes and expression usages are
confusing in xml dsl, so if we have t
Github user vrlgohel closed the pull request at:
https://github.com/apache/camel/pull/1844
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
GitHub user vrlgohel opened a pull request:
https://github.com/apache/camel/pull/1845
CAMEL-10126: Refactored completionSize & completionTimeout expressions
completionTimeout & completionSize attributes and expression usages are
confusing in xml dsl, so if we have to ch
Github user vrlgohel closed the pull request at:
https://github.com/apache/camel/pull/1845
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
