use these libraries they can be found at Maven Central, please refer to the client class path documentation for more information. 2. We removed ActiveMQ-Artemis rest as part of 2.26.0. If you still require its latest version at Maven central. You can still follow the steps on Rest from any previous documentation, however you should stop using the module as it will not be maintained any more. 3. We removed customize the index page or to add custom content in the web folder please refer to the web-server documentation for more information on disabling the redirect and enabling the web content. 2.25.0 Full release

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. user-manual - The user manual is placed under the web folder The filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. STOMP and JMS interoperability Sending and consuming STOMP message from JMS or Core API STOMP

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. user-manual - The user manual is placed under the web folder The filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. STOMP and JMS interoperability Sending and consuming STOMP message from JMS or Core API STOMP

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. user-manual - The user manual is placed under the web folder filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. STOMP and JMS interoperability Sending and consuming STOMP message from JMS or Core API STOMP

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. user-manual - The user manual is placed under the web folder The filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. STOMP and JMS interoperability Sending and consuming STOMP message from JMS or Core API STOMP

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. Using the Server 31 user-manual - The user manual is placed prefix: queue waypoint: yes } For more information refer to the "brokered messaging" documentation for Apache Qpid Dispatch Router. Important: Do not use this feature to connect to another broker

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. Using the Server 32 user-manual - The user manual is placed prefix: queue waypoint: yes } For more information refer to the "brokered messaging" documentation for Apache Qpid Dispatch Router. Important: Do not use this feature to connect to another broker

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. user-manual - The user manual is placed under the web folder filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. STOMP and JMS interoperability Sending and consuming STOMP message from JMS or Core API STOMP

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. user-manual - The user manual is placed under the web folder filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. STOMP and JMS interoperability Sending and consuming STOMP message from JMS or Core API STOMP

org/schema"/> This configures role based authorisation for JMX. Read more in the Management documentation. 2. If configured, remove the Jolokia war file from the web element in /etc/bootstrap files web - The folder where the web context is loaded when the broker runs. api - The api documentation is placed under the web folder. user-manual - The user manual is placed under the web folder filter expression syntax follows the core filter syntax described in the Filter Expressions documentation. STOMP and JMS interoperability Sending and consuming STOMP message from JMS or Core API STOMP