. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 10.2. Core API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 12. Mapping JMS Concepts to the Core API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 28.1. The Management API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 10.2. Core API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 12. Mapping JMS Concepts to the Core API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 28.1. The Management API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 10.2. Core API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 12. Mapping JMS Concepts to the Core API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 28.1. The Management API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 10.2. Core API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 12. Mapping JMS Concepts to the Core API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 28.1. The Management API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping JMS Concepts to the Core API Using JMS The Client Classpath JMS Jakarta Examples Routing Messages With Wild Cards Wildcard migrating your instance to a newer version. The client and broker now use SLF4J for their logging API. The broker distribution now uses Log4J 2 as its logging implementation. Upgrading from older versions older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2

Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping JMS Concepts to the Core API Using JMS The Client Classpath JMS Jakarta Examples Routing Messages With Wild Cards Wildcard migrating your instance to a newer version. The client and broker now use SLF4J for their logging API. The broker distribution now uses Log4J 2 as its logging implementation. Upgrading from older versions older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2

Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping JMS Concepts to the Core API Using JMS The Client Classpath JMS Jakarta Examples Routing Messages With Wild Cards Wildcard migrating your instance to a newer version. The client and broker now use SLF4J for their logging API. The broker distribution now uses Log4J 2 as its logging implementation. Upgrading from older versions older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2

Interoperability AMQP Broker Connections MQTT STOMP OpenWire Core Mapping JMS Concepts to the Core API Using JMS The Client Classpath JMS Jakarta Examples Routing Messages With Wild Cards Wildcard migrating your instance to a newer version. The client and broker now use SLF4J for their logging API. The broker distribution now uses Log4J 2 as its logging implementation. Upgrading from older versions older files it changes to an old-config-bkp. folder within the instance dir. Similarly, if you had customised the old logging.properties file you may need to prepare analogous changes for the new log4j2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 10.2. Core API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 12. Mapping JMS Concepts to the Core API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 28.1. The Management API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 10.2. Core API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 12. Mapping JMS Concepts to the Core API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 27.1. The Management API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .