[
https://issues.apache.org/jira/browse/AMQ-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16178756#comment-16178756
]
Claus Ibsen commented on AMQ-6822:
----------------------------------
This may only happen if a you use an older JMS client where I accidently had
mixed version of 5.14.5 and 5.15.0. After correcting this I don't see that
setDQL API error anymore.
> ActiveMQDestination has API breaking in setDLQ method
> -----------------------------------------------------
>
> Key: AMQ-6822
> URL: https://issues.apache.org/jira/browse/AMQ-6822
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.15.0
> Reporter: Claus Ibsen
>
> In older versions the setDQL method has no args
> http://activemq.apache.org/maven/5.14.5/apidocs/org/apache/activemq/command/ActiveMQDestination.html#setDLQ()
> But from 5.15.0 onwards it has a boolean arg (I guess to make it like a
> getter/setter)
> http://activemq.apache.org/maven/5.15.0/apidocs/org/apache/activemq/command/ActiveMQDestination.html#setDLQ-boolean-
> But the old API is gone and you can get errors like
> {code}
> 2017-09-25 10:54:31,901 [0.1:51866@61616] WARN Service
> - Async error occurred: java.lang.NoSuchMethodError:
> org.apache.activemq.command.ActiveMQDestination.setDLQ()V
> {code}
> It would be good to add the old method back, and then maybe mark it as
> deprecated, but it should help make it more backwards compatible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
