All Projects → apache → qpid-jms

apache / qpid-jms

Licence: Apache-2.0 License
Mirror of Apache Qpid JMS

Programming Languages

java
68154 projects - #9 most used programming language

Projects that are alternatives of or similar to qpid-jms

qpid-broker-j
Mirror of Apache Qpid Broker-J
Stars: ✭ 52 (-13.33%)
Mutual labels:  amqp, messaging, apache, amqp10, qpid, amqps
qpid-cpp
Mirror of Apache Qpid C++
Stars: ✭ 77 (+28.33%)
Mutual labels:  amqp, messaging, apache, amqp10, qpid, amqps
qpid-dispatch
Mirror of Apache Qpid Dispatch
Stars: ✭ 62 (+3.33%)
Mutual labels:  amqp, messaging, apache, amqp10, qpid, amqps
qpid-python
Mirror of Apache Qpid Python
Stars: ✭ 15 (-75%)
Mutual labels:  amqp, messaging, apache, qpid, amqps
qpid-proton-j
Mirror of Apache Qpid Proton-J
Stars: ✭ 28 (-53.33%)
Mutual labels:  amqp, messaging, apache, amqp10, qpid
Azure Event Hubs
☁️ Cloud-scale telemetry ingestion from any stream of data with Azure Event Hubs
Stars: ✭ 233 (+288.33%)
Mutual labels:  amqp, messaging, apache
azure-service-bus-go
Golang library for Azure Service Bus -- https://aka.ms/azsb
Stars: ✭ 67 (+11.67%)
Mutual labels:  amqp, messaging, amqp10
Activemq Artemis
Mirror of Apache ActiveMQ Artemis
Stars: ✭ 685 (+1041.67%)
Mutual labels:  amqp, messaging, apache
Qpid Proton
Mirror of Apache Qpid Proton
Stars: ✭ 164 (+173.33%)
Mutual labels:  amqp, messaging, apache
Azure Service Bus Dotnet
☁️ .NET Standard client library for Azure Service Bus
Stars: ✭ 237 (+295%)
Mutual labels:  amqp, messaging
azure-service-bus-java
☁️ Java client library for Azure Service Bus
Stars: ✭ 61 (+1.67%)
Mutual labels:  amqp, messaging
aop
AMQP on Pulsar protocol handler
Stars: ✭ 93 (+55%)
Mutual labels:  amqp, messaging
Enmasse
EnMasse - Self-service messaging on Kubernetes and OpenShift
Stars: ✭ 185 (+208.33%)
Mutual labels:  amqp, messaging
gobroker
golang wrapper for all (to-be) kinds of message brokers
Stars: ✭ 15 (-75%)
Mutual labels:  amqp, messaging
azure-event-hubs-java
☁️ Java client library for Azure Event Hubs
Stars: ✭ 49 (-18.33%)
Mutual labels:  amqp, messaging
messaging-replication
eXist-db JMS based messaging and document replication extension (JMS based)
Stars: ✭ 14 (-76.67%)
Mutual labels:  jms, messaging
rabbitmq-jms-client
RabbitMQ JMS client
Stars: ✭ 51 (-15%)
Mutual labels:  jms, messaging
amq-examples
This repository contains a set of examples to be used with Red Hat AMQ messaging suite components.
Stars: ✭ 25 (-58.33%)
Mutual labels:  amqp, messaging
Laravel Queue
Laravel Enqueue message queue extension. Supports AMQP, Amazon SQS, Kafka, Google PubSub, Redis, STOMP, Gearman, Beanstalk and others
Stars: ✭ 155 (+158.33%)
Mutual labels:  amqp, messaging
azure-event-hubs-go
Golang client library for Azure Event Hubs https://azure.microsoft.com/services/event-hubs
Stars: ✭ 80 (+33.33%)
Mutual labels:  amqp, messaging

Qpid JMS

Qpid JMS is a JMS 2.0 client that uses the AMQP 1.0 protocol, enabling it to interact with various AMQP 1.0 servers.

Below are some quick pointers you might find useful.

Building the code

The project requires Maven 3. Some example commands follow.

Clean previous builds output and install all modules to local repository without running the tests:

mvn clean install -DskipTests

Install all modules to the local repository after running all the tests:

mvn clean install

Perform a subset tests on the packaged release artifacts without installing:

mvn clean verify -Dtest=TestNamePattern*

Execute the tests and produce code coverage report:

mvn clean test jacoco:report

Examples

First build and install all the modules as detailed above (if running against a source checkout/release, rather than against released binaries) and then consult the README in the qpid-jms-examples module itself.

Documentation

Documentation source can be found in the qpid-jms-docs module, with a published version available on the website.

Distribution assemblies

After building the modules, src and binary distribution assemblies can be found at:

apache-qpid-jms/target
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].