As part of the NMS.AMQP project I can assure you that there is no intent to replace any transport other than AMQP. The NMS API is a general .NET API modeled after JMS. It can support a variety of transports (wireline implementations), one of which is selected when you instantiate an instance via the connection factory. If you look into the NMS API ( https://github.com/apache/activemq-nms-api) there are currently 10 transports supported one of which is AMQP.
The NMS.AMQP project simply seeks to update the AMQP part of the implementation, which had grown stale, with the AMQPNetLite open source project. I can't speak to the openWire transport, or AMQ7. As suggested otherwise you would be best to contact the authors of those transports to see their intentions for maintaining a module for the NMS API. Regards, Ragnar On Mon, Aug 27, 2018 at 8:47 PM dbeavon <[email protected]> wrote: > The bugs I was encountering while connecting from NMS clients were exposed > as > error messages in the broker logs. They appeared to be Artemis bugs. > > This doesn't have to be a redhat-specific question. I can rephrase if you > like. Is Apache Artemis supposed to be allowing connectivity from > NMS-openwire clients? (If not, I assume there are incompatibilities that > affect NMS and not JMS.) > > 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 see that one of my issues with NMS appears to have been fixed back in > February. https://issues.jboss.org/browse/ENTMQBR-836 > > Is there any reason for me to avoid using NMS with Artemis, or should I > give > it another shot? As I pointed out earlier, there were discussions about > rebuilding the NMS API on top of AMQP, but I'd prefer to keep using the > "openwire" variety of NMS as long as it is supported with Artemis. > > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-Dev-f2368404.html >
