History

Clebert Suconic 4ad830fb95 Bumping artemis as 3.0 After removing ActiveMQ Artemis rest (per ARTEMIS-3987), we should start promoting Artemis as 3.0		2022-09-12 15:09:31 -04:00
..
src/main/java/org/apache/activemq/artemis/jms/example	ARTEMIS-2888 ARTEMIS-2859 ARTEMIS-2768 - revert new page-store-name addressSetting, when the page store respects the target address and the size is tallied on the target address store, it is no longer neecessary	2020-10-19 14:04:35 +01:00
pom.xml	Bumping artemis as 3.0	2022-09-12 15:09:31 -04:00
readme.md	ARTEMIS-2888 ARTEMIS-2859 ARTEMIS-2768 - revert new page-store-name addressSetting, when the page store respects the target address and the size is tallied on the target address store, it is no longer neecessary	2020-10-19 14:04:35 +01:00

readme.md

Topic Hierarchy Example

To run the example, simply type mvn verify from this directory, or mvn -PnoServer verify if you want to start and create the broker manually.

ActiveMQ Artemis supports topic hierarchies. With a topic hierarchy you can register a subscriber with a wild-card and that subscriber will receive any messages routed to an address that match the wildcard.

ActiveMQ Artemis wild-cards can use the character # which means "match any number of words", and the character * which means "match a single word". Words are delimited by the character ..

For example if I subscribe using the wild-card news.europe.#, then that would match messages sent to the addresses news.europe, news.europe.sport and news.europe.entertainment, but it does not match messages sent to the address news.usa.wrestling.

For more information on the wild-card syntax please consult the user manual.