Support JMS ObjectMessage

Fixes #2599

docs/modules/ROOT/pages/reference/extensions/activemq.adoc

@@ -39,6 +39,19 @@ Or add the coordinates to your existing project:
 
 Check the xref:user-guide/index.adoc[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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.
+
+
 == 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 

docs/modules/ROOT/pages/reference/extensions/amqp.adoc

@@ -39,6 +39,19 @@ Or add the coordinates to your existing project:
 
 Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
 
+== Usage
+
+=== Message mapping with `org.w3c.dom.Node`
+
+The Camel AMQP 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.
+
+
 == Additional Camel Quarkus configuration
 
 The extension leverages the https://github.com/amqphub/quarkus-qpid-jms/[Quarkus Qpid JMS] extension. A ConnectionFactory bean is automatically created

docs/modules/ROOT/pages/reference/extensions/jms.adoc

@@ -46,3 +46,8 @@ Check the xref:user-guide/index.adoc[User guide] for more information about writ
 The Camel JMS 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.
+

docs/modules/ROOT/pages/reference/extensions/sjms.adoc

@@ -38,3 +38,16 @@ Or add the coordinates to your existing project:
 ----
 
 Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
+
+== Usage
+
+=== Message mapping with `org.w3c.dom.Node`
+
+The Camel SJMS 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.
+

docs/modules/ROOT/pages/reference/extensions/sjms2.adoc

@@ -38,3 +38,16 @@ Or add the coordinates to your existing project:
 ----
 
 Check the xref:user-guide/index.adoc[User guide] for more information about writing Camel Quarkus applications.
+
+== Usage
+
+=== Message mapping with `org.w3c.dom.Node`
+
+The Camel SJMS2 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.
+

extensions/activemq/runtime/src/main/doc/usage.adoc

@@ -0,0 +1,9 @@
+=== 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.

extensions/amqp/runtime/src/main/doc/usage.adoc

@@ -0,0 +1,9 @@
+=== Message mapping with `org.w3c.dom.Node`
+
+The Camel AMQP 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.

extensions/jms/deployment/src/main/java/org/apache/camel/quarkus/component/jms/deployment/JmsProcessor.java

@@ -18,6 +18,7 @@
 
 import io.quarkus.deployment.annotations.BuildStep;
 import io.quarkus.deployment.builditem.FeatureBuildItem;
+import org.apache.camel.quarkus.core.deployment.spi.CamelSerializationBuildItem;
 
 class JmsProcessor {
 
@@ -28,4 +29,8 @@ FeatureBuildItem feature() {
         return new FeatureBuildItem(FEATURE);
     }
 
+    @BuildStep
+    CamelSerializationBuildItem serialization() {
+        return new CamelSerializationBuildItem();
+    }
 }

extensions/jms/runtime/src/main/doc/usage.adoc

@@ -2,3 +2,8 @@
 
 The Camel JMS 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.

extensions/sjms/deployment/src/main/java/org/apache/camel/quarkus/component/sjms/deployment/CamelSjmsProcessor.java

@@ -18,6 +18,7 @@
 
 import io.quarkus.deployment.annotations.BuildStep;
 import io.quarkus.deployment.builditem.FeatureBuildItem;
+import org.apache.camel.quarkus.core.deployment.spi.CamelSerializationBuildItem;
 
 public class CamelSjmsProcessor {
     private static final String FEATURE = "camel-sjms";
@@ -26,4 +27,9 @@ public class CamelSjmsProcessor {
     FeatureBuildItem feature() {
         return new FeatureBuildItem(FEATURE);
     }
+
+    @BuildStep
+    CamelSerializationBuildItem serialization() {
+        return new CamelSerializationBuildItem();
+    }
 }

extensions/sjms/runtime/src/main/doc/usage.adoc

@@ -0,0 +1,9 @@
+=== Message mapping with `org.w3c.dom.Node`
+
+The Camel SJMS 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.

extensions/sjms2/deployment/src/main/java/org/apache/camel/quarkus/component/sjms2/deployment/CamelSjms2Processor.java

@@ -18,6 +18,7 @@
 
 import io.quarkus.deployment.annotations.BuildStep;
 import io.quarkus.deployment.builditem.FeatureBuildItem;
+import org.apache.camel.quarkus.core.deployment.spi.CamelSerializationBuildItem;
 
 public class CamelSjms2Processor {
     private static final String FEATURE = "camel-sjms2";
@@ -26,4 +27,9 @@ public class CamelSjms2Processor {
     FeatureBuildItem feature() {
         return new FeatureBuildItem(FEATURE);
     }
+
+    @BuildStep
+    CamelSerializationBuildItem serialization() {
+        return new CamelSerializationBuildItem();
+    }
 }

extensions/sjms2/runtime/src/main/doc/usage.adoc

@@ -0,0 +1,9 @@
+=== Message mapping with `org.w3c.dom.Node`
+
+The Camel SJMS2 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 xref:user-guide/native-mode.adoc#serialization[native mode user guide] for more information.

integration-tests/messaging/src/main/java/org/apache/camel/quarkus/component/messaging/it/Person.java

@@ -18,6 +18,9 @@
 
 import java.io.Serializable;
 
+import io.quarkus.runtime.annotations.RegisterForReflection;
+
+@RegisterForReflection(serialization = true)
 public class Person implements Serializable {
     String name;
 

integration-tests/messaging/src/test/java/org/apache/camel/quarkus/component/messaging/it/JmsTest.java

@@ -24,7 +24,6 @@
 
 import io.quarkus.test.common.QuarkusTestResource;
 import io.quarkus.test.common.ResourceArg;
-import io.quarkus.test.junit.DisabledOnNativeImage;
 import io.quarkus.test.junit.QuarkusTest;
 import io.restassured.RestAssured;
 import io.restassured.http.ContentType;
@@ -152,7 +151,6 @@ public void testJmsSelector() {
     }
 
     @Test
-    @DisabledOnNativeImage("https://github.com/apache/camel-quarkus/issues/2599")
     public void testJmsObject() {
         String message = "Mr Test Person";
         RestAssured.given()
@@ -164,7 +162,6 @@ public void testJmsObject() {
     }
 
     @Test
-    @DisabledOnNativeImage("https://github.com/apache/camel-quarkus/issues/2599")
     public void testJmsTransferExchange() {
         String message = "Test transfer message";
         RestAssured.given()