Javax replaced with jakarta in adoc files #5293

apache · Sep 12, 2023 · 5144a43 · 5144a43
1 parent 6de0b81
commit 5144a43
Show file tree

Hide file tree

Showing 10 changed files with 35 additions and 35 deletions.
diff --git a/docs/modules/ROOT/pages/reference/extensions/activemq.adoc b/docs/modules/ROOT/pages/reference/extensions/activemq.adoc
@@ -50,13 +50,13 @@ endif::[]
 [id="extensions-activemq-usage-message-mapping-with-org-w3c-dom-node"]
 === 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`,
+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-activemq-usage-native-mode-support-for-javax-jms-objectmessage"]
-=== Native mode support for javax.jms.ObjectMessage
+[id="extensions-activemq-usage-native-mode-support-for-jakarta-jms-objectmessage"]
+=== Native mode support for jakarta.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)`. 
+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.
 
 

diff --git a/docs/modules/ROOT/pages/reference/extensions/amqp.adoc b/docs/modules/ROOT/pages/reference/extensions/amqp.adoc
@@ -50,13 +50,13 @@ endif::[]
 [id="extensions-amqp-usage-message-mapping-with-org-w3c-dom-node"]
 === 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`,
+The Camel AMQP 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-amqp-usage-native-mode-support-for-javax-jms-objectmessage"]
-=== Native mode support for javax.jms.ObjectMessage
+[id="extensions-amqp-usage-native-mode-support-for-jakarta-jms-objectmessage"]
+=== Native mode support for jakarta.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)`. 
+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-amqp-usage-connection-pooling"]

diff --git a/docs/modules/ROOT/pages/reference/extensions/jms.adoc b/docs/modules/ROOT/pages/reference/extensions/jms.adoc
@@ -50,13 +50,13 @@ endif::[]
 [id="extensions-jms-usage-message-mapping-with-org-w3c-dom-node"]
 === Message mapping with `org.w3c.dom.Node`
 
-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`, 
+The Camel JMS 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-jms-usage-native-mode-support-for-javax-jms-objectmessage"]
-=== Native mode support for javax.jms.ObjectMessage
+[id="extensions-jms-usage-native-mode-support-for-jakarta-jms-objectmessage"]
+=== Native mode support for jakarta.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)`. 
+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-jms-usage-support-for-connection-pooling-and-x-open-xa-distributed-transactions"]

diff --git a/docs/modules/ROOT/pages/reference/extensions/sjms.adoc b/docs/modules/ROOT/pages/reference/extensions/sjms.adoc
@@ -50,13 +50,13 @@ endif::[]
 [id="extensions-sjms-usage-message-mapping-with-org-w3c-dom-node"]
 === 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`,
+The Camel SJMS 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-sjms-usage-native-mode-support-for-javax-jms-objectmessage"]
-=== Native mode support for javax.jms.ObjectMessage
+[id="extensions-sjms-usage-native-mode-support-for-jakarta-jms-objectmessage"]
+=== Native mode support for jakarta.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)`. 
+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.
 
 

diff --git a/docs/modules/ROOT/pages/reference/extensions/sjms2.adoc b/docs/modules/ROOT/pages/reference/extensions/sjms2.adoc
@@ -50,13 +50,13 @@ endif::[]
 [id="extensions-sjms2-usage-message-mapping-with-org-w3c-dom-node"]
 === 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`,
+The Camel SJMS2 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-sjms2-usage-native-mode-support-for-javax-jms-objectmessage"]
-=== Native mode support for javax.jms.ObjectMessage
+[id="extensions-sjms2-usage-native-mode-support-for-jakarta-jms-objectmessage"]
+=== Native mode support for jakarta.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)`. 
+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.
 
 

diff --git a/extensions/activemq/runtime/src/main/doc/usage.adoc b/extensions/activemq/runtime/src/main/doc/usage.adoc
@@ -1,9 +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`,
+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.
 
-=== Native mode support for javax.jms.ObjectMessage
+=== Native mode support for jakarta.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)`. 
+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.
diff --git a/extensions/amqp/runtime/src/main/doc/usage.adoc b/extensions/amqp/runtime/src/main/doc/usage.adoc
@@ -1,11 +1,11 @@
 === 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`,
+The Camel AMQP 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.
 
-=== Native mode support for javax.jms.ObjectMessage
+=== Native mode support for jakarta.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)`. 
+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.
 
 === Connection Pooling

diff --git a/extensions/jms/runtime/src/main/doc/usage.adoc b/extensions/jms/runtime/src/main/doc/usage.adoc
@@ -1,11 +1,11 @@
 === Message mapping with `org.w3c.dom.Node`
 
-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`, 
+The Camel JMS 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.
 
-=== Native mode support for javax.jms.ObjectMessage
+=== Native mode support for jakarta.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)`. 
+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.
 
 === Support for Connection pooling and X/Open XA distributed transactions

diff --git a/extensions/sjms/runtime/src/main/doc/usage.adoc b/extensions/sjms/runtime/src/main/doc/usage.adoc
@@ -1,9 +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`,
+The Camel SJMS 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.
 
-=== Native mode support for javax.jms.ObjectMessage
+=== Native mode support for jakarta.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)`. 
+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.
diff --git a/extensions/sjms2/runtime/src/main/doc/usage.adoc b/extensions/sjms2/runtime/src/main/doc/usage.adoc
@@ -1,9 +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`,
+The Camel SJMS2 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.
 
-=== Native mode support for javax.jms.ObjectMessage
+=== Native mode support for jakarta.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)`. 
+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.