History

Michael Davis f5805b83d2 Khepri: Handle breaking change in khepri adv API return type [Why] All callers of `khepri_adv` and `khepri_tx_adv` need updates to handle the now uniform return type of `khepri:node_props_map()` in Khepri 0.17.0. [How] We don't need any compatibility code to handle "either the old return type or the new return type" from the khepri_adv API because the translation is done entirely in the "client side" code in Khepri - meaning that the return value from the Ra server is the same but it is translated differently by the functions in `khepri_adv`. However, we need to adapt transaction functions because they may be executed on different versions of Khepri and the behaviour of `khepri_tx_adv` can be different. To take the possible change of return value format, we use the new `khepri_tx:does_api_comply_with/1` to know what to expect.		2025-04-08 18:47:27 +02:00
..
include	Bump (c) line year	2025-01-01 17:54:10 -05:00
src	Khepri: Handle breaking change in khepri adv API return type	2025-04-08 18:47:27 +02:00
test	Bump (c) line year	2025-01-01 17:54:10 -05:00
CODE_OF_CONDUCT.md	Replace files with symlinks	2022-04-15 06:04:29 -07:00
CONTRIBUTING.md	Replace files with symlinks	2022-04-15 06:04:29 -07:00
LICENSE	Replace @rabbitmq.com addresses with rabbitmq-core@groups.vmware.com	2023-06-20 15:40:13 +04:00
LICENSE-MPL-RabbitMQ	Revert drop of Exhibit B on MPL 2.0	2020-07-20 17:00:15 +01:00
Makefile	Add mnesia to LOCAL_DEPS in rabbitmq_jms_topic_exchange	2023-10-16 18:10:50 +02:00
README.md	Bump (c) line year	2025-01-01 17:54:10 -05:00

README.md

RabbitMQ JMS Topic Exchange Plugin

Overview

This plugin adds server-side support for RabbitMQ JMS client. This plugin provides support for JMS topic routing and selection based on JMS SQL selection rules.

This implementation is based upon the Java Messaging Service Specification Version 1.1.

Project Maturity

RabbitMQ JMS-related projects are several years old and can be considered reasonably mature. They have been first open sourced in June 2016. Some related projects (e.g. a compliance test suite) and documentation are yet to be open sourced.

Supported RabbitMQ Versions

This plugin ships with RabbitMQ.

Installation

Like all other plugins, this plugin must be enabled before it can be used. Enable it with

[sudo] rabbitmq-plugins enable rabbitmq_jms_topic_exchange

Design

The plugin this generates is a user-written exchange type for RabbitMQ client use. The exchange type name is "x-jms-topic" but this is not a topic exchange. Instead it works together with a standard topic exchange to provide the JMS topic selection function.

When JMS Selectors are used on a Topic Destination consumer, the destination (queue) is bound to an exchange of type x-jms-topic, with arguments that indicate what the selection criteria are. The x-jms-topic exchange is, in turn, bound to the standard Topic Exchange used by JMS messaging (this uses the RabbitMQ exchange-to-exchange binding extension to the AMQP 0-9-1 protocol).

In this way, normal topic routing can occur, with the overhead of selection only applying when selection is used, and after the routing and filtering implied by the topic name.

Copyright and License

See LICENSE for license information.