You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/04/09 13:37:05 UTC

[jira] [Commented] (CAMEL-3556) Add callback feature to prepare copy of Exchange for multicast, recipient list EIPs

    [ https://issues.apache.org/jira/browse/CAMEL-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017838#comment-13017838 ] 

Claus Ibsen commented on CAMEL-3556:
------------------------------------

You may also want this on WireTap EIP. So it are potential other EIPs as well.

We could just use the process API which allows end user access to the Exchange where they can manipulate the payload beforehand.


> Add callback feature to prepare copy of Exchange for multicast, recipient list EIPs
> -----------------------------------------------------------------------------------
>
>                 Key: CAMEL-3556
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3556
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.8.0
>
>
> Those EIPs copy the incoming Exchange which is send to the recipients.
> The copy is a reference copy of the message payload. In some cased end users may need to do a deep clone copy or control this copy process themselves.
> We should add a callback feature where they can do this.
> See nabble
> http://camel.465427.n5.nabble.com/Camel-2-5-Multicast-Component-Body-References-Concurrency-Copying-tp3339259p3339259.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira