camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hubertus Willuhn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-10965) Missing Intercept Call if using Multicast
Date Thu, 09 Mar 2017 06:52:38 GMT

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

Hubertus Willuhn commented on CAMEL-10965:
------------------------------------------

Sorry for replying, but I want to clarify this: So the endpoint uri must be equal over all
references (including parameters)? I already knew this for example with SEDA endpoints and
the concurrentConsumer parameters were its meaningful. However the option failIfNoConsumers
should only apply to the producer or am I wrong?

> 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)

Mime
View raw message