ActiveMQ

JVM since1.0.0 Native since1.0.0

Send messages to (or consume from) Apache ActiveMQ. This component extends the Camel JMS component.

What’s inside

Please refer to the above link for usage and configuration details.

Maven coordinates

Or add the coordinates to your existing project:

<dependency>
    <groupId>org.apache.camel.quarkus</groupId>
    <artifactId>camel-quarkus-activemq</artifactId>
</dependency>

Check the User guide for more information about writing Camel Quarkus applications.

Usage

Message mapping with org.w3c.dom.Node

The Camel ActiveMQ component supports message mapping between javax.jms.Message and org.apache.camel.Message. When wanting to convert a Camel message body type of org.w3c.dom.Node, you must ensure that the camel-quarkus-jaxp extension is present on the classpath.

Native mode support for javax.jms.ObjectMessage

When sending JMS message payloads as javax.jms.ObjectMessage, you must annotate the relevant classes to be registered for serialization with @RegisterForReflection(serialization = true). Note that this extension automatically sets quarkus.camel.native.reflection.serialization-enabled = true for you. Refer to the native mode user guide for more information.

Camel Quarkus limitations

ActiveMQ XPath selectors are disabled in native mode as the functionality depends on activemq-broker. This dependency is excluded from the dependency tree, since none of the ActiveMQ broker functionality is supported in native mode.

SSL in native mode

This extension auto-enables SSL support in native mode. Hence you do not need to add quarkus.ssl.native=true to your application.properties yourself. See also Quarkus SSL guide.