You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by boday <be...@initekconsulting.com> on 2013/03/02 07:35:18 UTC

aggregator - force completion with header...

currently its implemented to only look for a header
(Exchange.AGGREGATION_COMPLETE_ALL_GROUPS) in a "signal" message and
excludes that message...

it was mentioned in the following SFO post to have the option to be
inclusive of the current message instead of just using it as a signal
message...seems like a reasonable request to me

http://stackoverflow.com/questions/15070864/apache-camel-make-aggregator-flush/15071536#comment21276998_15071536

so, my thought is to either add a new mode
(Exchange.AGGREGATION_COMPLETE_ALL_GROUPS_INCLUSIVE, etc) or just make the
current mode inclusive of the current message instead of skipping it...

any thoughts on this?




-----
Ben O'Day
IT Consultant -http://consulting-notes.com

--
View this message in context: http://camel.465427.n5.nabble.com/aggregator-force-completion-with-header-tp5728368.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: aggregator - force completion with header...

Posted by boday <be...@initekconsulting.com>.
thanks for the feedback guys, created the following ticket and will add
support soon:

https://issues.apache.org/jira/browse/CAMEL-6119



-----
Ben O'Day
IT Consultant -http://consulting-notes.com

--
View this message in context: http://camel.465427.n5.nabble.com/aggregator-force-completion-with-header-tp5728368p5728377.html
Sent from the Camel Development mailing list archive at Nabble.com.

Re: aggregator - force completion with header...

Posted by Raul Kripalani <ra...@evosent.com>.
A third option would be to create an option in the aggregator. A bit more
work, but cleaner IMHO.

Sent while on the move.
On 2 Mar 2013 06:58, "Claus Ibsen" <cl...@gmail.com> wrote:

> Hi
>
> Yeah that may seem like a good idea. But you cannot change the current
> behavior (break stuff for people). So I suggest to add that 2nd header
> so you can say its inclusive.
>
>
>
> On Sat, Mar 2, 2013 at 7:35 AM, boday <be...@initekconsulting.com>
> wrote:
> > currently its implemented to only look for a header
> > (Exchange.AGGREGATION_COMPLETE_ALL_GROUPS) in a "signal" message and
> > excludes that message...
> >
> > it was mentioned in the following SFO post to have the option to be
> > inclusive of the current message instead of just using it as a signal
> > message...seems like a reasonable request to me
> >
> >
> http://stackoverflow.com/questions/15070864/apache-camel-make-aggregator-flush/15071536#comment21276998_15071536
> >
> > so, my thought is to either add a new mode
> > (Exchange.AGGREGATION_COMPLETE_ALL_GROUPS_INCLUSIVE, etc) or just make
> the
> > current mode inclusive of the current message instead of skipping it...
> >
> > any thoughts on this?
> >
> >
> >
> >
> > -----
> > Ben O'Day
> > IT Consultant -http://consulting-notes.com
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/aggregator-force-completion-with-header-tp5728368.html
> > Sent from the Camel Development mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Email: cibsen@redhat.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>

Re: aggregator - force completion with header...

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

Yeah that may seem like a good idea. But you cannot change the current
behavior (break stuff for people). So I suggest to add that 2nd header
so you can say its inclusive.



On Sat, Mar 2, 2013 at 7:35 AM, boday <be...@initekconsulting.com> wrote:
> currently its implemented to only look for a header
> (Exchange.AGGREGATION_COMPLETE_ALL_GROUPS) in a "signal" message and
> excludes that message...
>
> it was mentioned in the following SFO post to have the option to be
> inclusive of the current message instead of just using it as a signal
> message...seems like a reasonable request to me
>
> http://stackoverflow.com/questions/15070864/apache-camel-make-aggregator-flush/15071536#comment21276998_15071536
>
> so, my thought is to either add a new mode
> (Exchange.AGGREGATION_COMPLETE_ALL_GROUPS_INCLUSIVE, etc) or just make the
> current mode inclusive of the current message instead of skipping it...
>
> any thoughts on this?
>
>
>
>
> -----
> Ben O'Day
> IT Consultant -http://consulting-notes.com
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/aggregator-force-completion-with-header-tp5728368.html
> Sent from the Camel Development mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen