[
https://issues.apache.org/jira/browse/ARTEMIS-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695224#comment-16695224
]
ASF GitHub Bot commented on ARTEMIS-2178:
-----------------------------------------
Github user michaelandrepearce commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/2438#discussion_r235527477
--- Diff:
artemis-server/src/main/java/org/apache/activemq/artemis/core/config/BridgeConfiguration.java
---
@@ -75,6 +76,8 @@
// The bridge shouldn't be sending blocking anyways
private long callTimeout = ActiveMQClient.DEFAULT_CALL_TIMEOUT;
+ private ComponentConfigurationRoutingType routingType =
ComponentConfigurationRoutingType.valueOf(ActiveMQDefaultConfiguration.getDefaultDivertRoutingType());
--- End diff --
Should this not be default bridge routing type? (looks like picking up the
divert default)
> Support routing-type configuration on core bridge
> -------------------------------------------------
>
> Key: ARTEMIS-2178
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2178
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
>
> {{MULTICAST}} messages forwarded by a core bridge will not be routed to any
> {{ANYCAST}} queues and vice-versa. Diverts have the ability to configure how
> routing-type is treated. Core bridges should support this same kind of
> functionality.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
