For more information, see Qpid JMS AMQP 1.0.
JMS JAR names and versions might have changed.
#APACHE JMETER RABBITMQ PLUGIN HOW TO#
For more information about how to create Service Bus namespaces and queues, see Get started with Service Bus queues. If you don't, you can create the namespace and queue by using the Azure portal. This article assumes that you already have a Service Bus namespace that contains a queue named basicqueue. You also can build applications composed of components built by using a mix of languages, frameworks, and operating systems. Support for AMQP 1.0 in Service Bus means that you can use the queuing and publish or subscribe brokered messaging features from a range of platforms by using an efficient binary protocol. You can use these two articles together to learn about cross-platform messaging using the Advanced Message Queuing Protocol (AMQP) 1.0.ĪMQP 1.0 is an efficient, reliable, wire-level messaging protocol that you can use to build robust, cross-platform messaging applications. A companion article explains how to do the same by using the Azure Service Bus. These messaging features include queues and publishing or subscribing to topics. This article explains how to use Service Bus messaging features from Java applications by using the popular JMS API standard. This article caters to limited support for the Java Message Service (JMS) 1.1 API and exists for the Azure Service Bus standard tier only.įull support for the Java Message Service 2.0 API is available only on the Azure Service Bus premium tier in preview.
0 kommentar(er)
