activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jostbg <...@git.apache.org>
Subject [GitHub] activemq-artemis issue #1775: ARTEMIS-1587 Add setting to control the queue ...
Date Mon, 15 Jan 2018 10:49:05 GMT
Github user jostbg commented on the issue:

    https://github.com/apache/activemq-artemis/pull/1775
  
    So when we pre-define non-durable anycast queues in Artemis and a JMS client publishes
to that queue or subscribes to it, we are actually already violating the JMS spec. Therefore
it would no be different if the non-durable queue is pre-defined or auto-created.
    
    In our case we do not really care about the JMS spec. We only use the Qpid AMQP JMS client
because it seems to be the only actually working and easy to use AMQP 1.0 client for Java.
We tried IBM's mqlight which we didn't get to work in our scenario and also it seems to be
dead (no development since 2016). SwiftMQ has an odd non-OSS license/distribution model. And
proton-j is just too bare bone without proper documentation.


---

Mime
View raw message