You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ja...@apache.org on 2023/09/12 12:01:00 UTC
[camel-quarkus] branch 3.2.x updated: Javax replaced with jakarta in adoc files #5293
This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch 3.2.x
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/3.2.x by this push:
new 0632db415b Javax replaced with jakarta in adoc files #5293
0632db415b is described below
commit 0632db415b2074bbc4ff9c9e960b930e71d56a78
Author: JiriOndrusek <on...@gmail.com>
AuthorDate: Tue Sep 12 11:46:38 2023 +0200
Javax replaced with jakarta in adoc files #5293
---
docs/modules/ROOT/pages/reference/extensions/activemq.adoc | 8 ++++----
docs/modules/ROOT/pages/reference/extensions/amqp.adoc | 8 ++++----
docs/modules/ROOT/pages/reference/extensions/jms.adoc | 8 ++++----
docs/modules/ROOT/pages/reference/extensions/sjms.adoc | 8 ++++----
docs/modules/ROOT/pages/reference/extensions/sjms2.adoc | 8 ++++----
extensions/activemq/runtime/src/main/doc/usage.adoc | 6 +++---
extensions/amqp/runtime/src/main/doc/usage.adoc | 6 +++---
extensions/jms/runtime/src/main/doc/usage.adoc | 6 +++---
extensions/sjms/runtime/src/main/doc/usage.adoc | 6 +++---
extensions/sjms2/runtime/src/main/doc/usage.adoc | 6 +++---
10 files changed, 35 insertions(+), 35 deletions(-)
diff --git a/docs/modules/ROOT/pages/reference/extensions/activemq.adoc b/docs/modules/ROOT/pages/reference/extensions/activemq.adoc
index 068614c7c5..430c0383fd 100644
--- 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
index 97dd753142..93c61145e2 100644
--- 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
index d66090385c..678d7edfb2 100644
--- 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
index 801155fe7c..2be632026c 100644
--- 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
index 15fda612e4..7bd1308780 100644
--- 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
index 3fd59c5fa5..264d21d7c6 100644
--- 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
index 3ce81fcee9..258357644d 100644
--- 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
index 1f9bd066ea..582028bcc5 100644
--- 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
index 11b8da971d..21c41d5d73 100644
--- 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
index ebc33960e4..edac8078ce 100644
--- 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.