You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@camel.apache.org by ychawla <pr...@gmail.com> on 2015/03/07 01:14:12 UTC

Multicast Position and Exchange Properties

Hello All,
I am multicasting and need to alter the document before I send it to
different endpoints.  To do this, I use onPrepareRef="myProcessor".  The
issue that I am running into is that the copy of the Exchange that I get
does not have much info other than a copy of the exchange.  It would be
helpful to have properties analogous to the splitter like:

CamelSplitIndex
CamelSplitSize
CamelSplitComplete

This is especially helpful for the recipient list.  You do get the
Exchange.TO_ENDPOINT.  Other than that, you just get a copy of the original
Exchange without any context.

I think it would be useful to have extra properties on the exchange similar
to the Split pattern.

Does this make sense?

Thanks!
Yogesh



--
View this message in context: http://camel.465427.n5.nabble.com/Multicast-Position-and-Exchange-Properties-tp5763768.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Multicast Position and Exchange Properties

Posted by ychawla <pr...@gmail.com>.

Thanks Claus,
This is exactly what I am looking for.  I will try to update the Multicast
WIKI so it shows these Exchange properties like it does on the Splitter WIKI
page.

-Yogesh



--
View this message in context: http://camel.465427.n5.nabble.com/Multicast-Position-and-Exchange-Properties-tp5763768p5764044.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Multicast Position and Exchange Properties

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

The multicast has index / complete. See the keys on exchange
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html

On Sat, Mar 7, 2015 at 1:14 AM, ychawla <pr...@gmail.com> wrote:
> Hello All,
> I am multicasting and need to alter the document before I send it to
> different endpoints.  To do this, I use onPrepareRef="myProcessor".  The
> issue that I am running into is that the copy of the Exchange that I get
> does not have much info other than a copy of the exchange.  It would be
> helpful to have properties analogous to the splitter like:
>
> CamelSplitIndex
> CamelSplitSize
> CamelSplitComplete
>
> This is especially helpful for the recipient list.  You do get the
> Exchange.TO_ENDPOINT.  Other than that, you just get a copy of the original
> Exchange without any context.
>
> I think it would be useful to have extra properties on the exchange similar
> to the Split pattern.
>
> Does this make sense?
>
> Thanks!
> Yogesh
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Multicast-Position-and-Exchange-Properties-tp5763768.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/