// Do not edit directly!
// This file was generated by camel-quarkus-maven-plugin:update-extension-doc-page
[id="extensions-activemq6"]
= ActiveMQ 6.x
:linkattrs:
:cq-artifact-id: camel-quarkus-activemq6
:cq-native-supported: true
:cq-status: Stable
:cq-status-deprecation: Stable
:cq-description: Send messages to (or consume from) Apache ActiveMQ 6.x. This component extends the Camel JMS component.
:cq-deprecated: false
:cq-jvm-since: 3.30.0
:cq-native-since: 3.30.0

ifeval::[{doc-show-badges} == true]
[.badges]
[.badge-key]##JVM since##[.badge-supported]##3.30.0## [.badge-key]##Native since##[.badge-supported]##3.30.0##
endif::[]

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

[id="extensions-activemq6-whats-inside"]
== What's inside

* xref:{cq-camel-components}::activemq6-component.adoc[ActiveMQ 6.x component], URI syntax: `activemq6:destinationType:destinationName`

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

[id="extensions-activemq6-maven-coordinates"]
== Maven coordinates

https://{link-quarkus-code-generator}/?extension-search=camel-quarkus-activemq6[Create a new project with this extension on {link-quarkus-code-generator}, window="_blank"]

Or add the coordinates to your existing project:

[source,xml]
----
<dependency>
    <groupId>org.apache.camel.quarkus</groupId>
    <artifactId>camel-quarkus-activemq6</artifactId>
</dependency>
----
ifeval::[{doc-show-user-guide-link} == true]
Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
endif::[]

[id="extensions-activemq6-usage"]
== Usage
[id="extensions-activemq6-usage-message-mapping-with-org-w3c-dom-node"]
=== Message mapping with `org.w3c.dom.Node`

The Camel ActiveMQ component supports message mapping between `jakarta.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-xml-jaxp` extension is present on the classpath.

[id="extensions-activemq6-usage-native-mode-support-for-jakarta-jms-objectmessage"]
=== Native mode support for jakarta.jms.ObjectMessage

When sending JMS message payloads as `jakarta.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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.


[id="extensions-activemq6-camel-quarkus-limitations"]
== Camel Quarkus limitations

ActiveMQ https://activemq.apache.org/selectors.html[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.


[id="extensions-activemq6-ssl-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
https://quarkus.io/guides/native-and-ssl[Quarkus SSL guide].

[id="extensions-activemq6-transferexception-option-in-native-mode"]
== transferException option in native mode

To use the `transferException` option in native mode, you must enable support for object serialization. Refer to the xref:user-guide/native-mode.adoc#serialization[native mode user guide]
for more information.

You will also need to enable serialization for the exception classes that you intend to serialize. For example.
[source,java]
----
@RegisterForReflection(targets = { IllegalStateException.class, MyCustomException.class }, serialization = true)
----
