Hi Justin, I appreciate the suggestion, but I don't consider that an option. What I want to do is expose the queues and topic of the internal jms-bus over MQTT. JMS is used extensively in my application and I currently expose access to those messages outside of the server using a http-wrapper: a pub/sub implementation using long-polling. I want to replace that with mqtt. Adding an external broker next to wildfly just to have MQTT-support, adds too much complexity: I'll have to synchronize the wildfly-internal jms-bus with this external one, in both directions. Or, alternatively, don't use the internal artemis anymore, and only rely on the external. That is probably even more work. Deployment doesn't become easier either. So you see, even if it is possible, it isn't all that simple, so it doesn't really help me :-)
Bottomline is, if I can't get MQTT up and running in wildfly, I won't be using it at all. Thomas -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
