> Is Apache Artemis supposed to be allowing connectivity from NMS-openwire clients?
I'm not aware of any specific testing done with NMS clients using the OpenWire provider and Artemis, but since Artemis supports OpenWire I would generally expect such clients to work. > The following lists a number of protocols and API's that are supported in Artemis: https://activemq.apache.org/artemis/ Note that there is no mention of NMS at all. I believe NMS is not mentioned here because it is just an API with providers who speak lots of different protocols. We don't list all the APIs which speak STOMP or AMQP because it is sufficient simply to list support for the protocols themselves (i.e. STOMP and AMQP). JMS is also just an API, but it is mentioned here as an exception because the broker actually ships with a JMS 1.1 & 2.0 client implementation. > Is there any reason for me to avoid using NMS with Artemis, or should I give it another shot? I assume you're asking specifically about the NMS API with the OpenWire provider. If that's the case, then I'm not aware of any reason you should avoid it. > ...I'd prefer to keep using the "openwire" variety of NMS as long as it is supported with Artemis. If implemented properly it really shouldn't matter what provider you use underneath the NMS API. They should all theoretically provide the same functionality. That's kind of the point of having an API in the first place (i.e. the implementation can change without impacting clients). Justin On Mon, Aug 27, 2018 at 8:12 PM, Clebert Suconic <[email protected]> wrote: > JBoss AMQ 7 is product from RedHat. > > You should ask Red Hat about it. > > On Fri, Aug 24, 2018 at 10:51 AM dbeavon <[email protected]> wrote: > > > Can someone please clear up some confusion for me about NMS on Jboss AMQ > 7 > > (Artemis)? > > > > I am confused about why it has been "deprecated". The Jboss AMQ release > > notes say that "NMS messaging APIs are deprecated in AMQ 7". About a > year > > ago I had done some of my own testing and ran into trouble fairly > quickly. > > It was pretty clear that I was probably one of the first to try running > an > > NMS client application that was connected to an Artemis broker. > > > > What is most unclear to me is why there is a double standard whereby > Jboss > > AMQ fully supports JMS clients that connect to the broker on the > "openwire" > > protocol, but they clearly discourage NMS clients that connect on the > same > > "openwire" protocol. It would seem to me that if AMQ 7 fully supports > the > > legacy JMS clients (based on "openwire"), then supporting NMS would only > be > > a minor amount of additional work. It almost seems like someone is going > > out of their way to give c# programmers a poke in the eye. > > > > > > I did find a document ("sneak preview") about AMQ 7 that said NMS legacy > > clients would be supported. Did they change their minds? See this link: > > > > https://www.redhat.com/files/summit/session-assets/2016/ > SS88848-sneak-preview-of-next-generation-messaging-platform- > red-hat-jboss-a-mq-7.pdf > > > > > > I am aware of a couple github projects (and related discussions) where > work > > is underway to rebuild NMS on top of "AMQP". > > > > https://github.com/apache/activemq-nms-amqp > > https://github.com/cjwmorgan-sol/nms-amqp > > > > > > > > http://activemq.2283324.n4.nabble.com/DISCUSS-Rework-NMS- > AMQP-td4721986i20.html > > > > http://activemq.2283324.n4.nabble.com/Reword-NMS-for- > AMQPNetLite-td4739536.html > > > > > > ... But this would all be unnecessary (or at least not very urgent) if > AMQ > > 7 > > fully supported NMS clients that are connecting via "openwire". In > short, > > I > > don't understand why Jboss AMQ 7 has deprecated NMS but not the > > corresponding JMS clients running on "openwire". They don't say JMS is > > deprecated and nor do they say "openwire" is deprecated... although I > found > > a blog that says openwire might one day be deprecated > > (https://blog.joshdreagan.com/2017/12/01/upgrading_amq_6_to_amq_7/). > > > > Should anyone be attempting to connecting a legacy NMS client application > > to > > AMQ 7? Or is that asking for trouble? Please help me understand if/how > c# > > client applications will need to be changed once an AMQ broker is > upgraded > > to AMQ 7. > > > > > > > > -- > > Sent from: > > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html > > > -- > Clebert Suconic >
