File: README.md

package info (click to toggle)
rabbitmq-server 4.0.5-6
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 37,948 kB
  • sloc: erlang: 257,835; javascript: 22,466; sh: 2,796; makefile: 2,517; python: 1,966; xml: 646; cs: 335; java: 244; ruby: 212; php: 100; perl: 63; awk: 13
file content (54 lines) | stat: -rw-r--r-- 1,958 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
# RabbitMQ JMS Topic Exchange Plugin

## Overview

This plugin adds server-side support for [RabbitMQ JMS client](https://github.com/rabbitmq/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](https://www.oracle.com/technetwork/java/docs-136352.html).

## 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

(c) 2007-2023 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

See [LICENSE](./LICENSE) for license information.