You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/03/08 17:39:38 UTC
[jira] [Commented] (CAMEL-10965) Missing Intercept Call if using
Multicast
[ https://issues.apache.org/jira/browse/CAMEL-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901630#comment-15901630 ]
Claus Ibsen commented on CAMEL-10965:
-------------------------------------
Its not the same endpoint, your intercept is not the same as the multicast. Use * as wildcard for intercept. See its doc
http://camel.apache.org/intercept
> Missing Intercept Call if using Multicast
> -----------------------------------------
>
> Key: CAMEL-10965
> URL: https://issues.apache.org/jira/browse/CAMEL-10965
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.17.1
> Reporter: Hubertus Willuhn
> Labels: interceptors, multicast, seda
> Attachments: CamelMulticastInterceptTest.java
>
>
> Calling an SEDA endpoint from another route using multicast will not call any {{interceptSendToEndpoint}} definition in the target route.
> I created a small test for this. See attachment.
> I think this is an unwanted behavior. However if using {{interceptFrom}} all is fine.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)