[
https://issues.apache.org/activemq/browse/CAMEL-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47693#action_47693
]
tim mcnamara commented on CAMEL-1131:
-------------------------------------
It would be trivial to create a multicast test similar to the custom
splitter. The problem is, this test would not expose the multicast
constructor bug as the validation is done against the type and not the
processor (where the problem lies). These tests need to cover both
cases - the problem I ran into, is that there was no obvious way to
get at the executor from the multicast processor.
> Invalid contructor intitialization in MulticastProcessor
> --------------------------------------------------------
>
> Key: CAMEL-1131
> URL: https://issues.apache.org/activemq/browse/CAMEL-1131
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.0.0
> Reporter: tim mcnamara
>
> parallelProcessing and executor being overridden in constructor.
> {code:title=MulticastProcessor.java|borderStyle=solid}
> public MulticastProcessor(Collection<Processor> processors,
> AggregationStrategy aggregationStrategy, boolean parallelProcessing,
> ThreadPoolExecutor executor) {
> this(processors, aggregationStrategy, false, null, false);
> }
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.