[
https://issues.apache.org/jira/browse/ARTEMIS-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582550#comment-14582550
]
Justin Bertram commented on ARTEMIS-109:
----------------------------------------
Looks like this functionality was inadvertently removed when the
DivertConfiguration was changed to a fluent class. I'll restore the previous
semantics.
> Divert routing name is no longer optional
> -----------------------------------------
>
> Key: ARTEMIS-109
> URL: https://issues.apache.org/jira/browse/ARTEMIS-109
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Jeff Mesnil
> Assignee: Justin Bertram
> Fix For: 1.0.1
>
>
> It used to be possible to create a divert configuration without a null
> routing name. The server was then generating a unique routing name instead.
> But now, it throws a NPE:
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.activemq.api.core.SimpleString.<init>(SimpleString.java:75)
> at
> org.apache.activemq.core.server.impl.ActiveMQServerImpl.deployDivert(ActiveMQServerImpl.java:1402)
> at
> org.apache.activemq.core.management.impl.ActiveMQServerControlImpl.createDivert(ActiveMQServerControlImpl.java:1805)
> {noformat}
> I have no idea what I should use as the routing name for my divert... (use
> its name, or the address or something different...)
> Either the API (and documentation) must be updated to reflect that the
> routing name is mandatory or the code to generate an unique one must be put
> back.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
