This is an automated email from the ASF dual-hosted git repository.

zhfeng pushed a commit to branch 2.13.x
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git


The following commit(s) were added to refs/heads/2.13.x by this push:
     new f2226561ae Backport jms doc 2.13.x (#4366)
f2226561ae is described below

commit f2226561aeb4b45d6e250f1a29647107f0f56fe1
Author: Zheng Feng <[email protected]>
AuthorDate: Wed Jan 4 10:24:25 2023 +0800

    Backport jms doc 2.13.x (#4366)
    
    * tidy up of jms extension documentation (#4327)
    
    * Regenerate the JMS doc page
    
    Co-authored-by: Peter Palaga <[email protected]>
---
 docs/modules/ROOT/pages/reference/extensions/jms.adoc | 11 +++++++----
 extensions/jms/runtime/src/main/doc/usage.adoc        |  9 ++++++---
 2 files changed, 13 insertions(+), 7 deletions(-)

diff --git a/docs/modules/ROOT/pages/reference/extensions/jms.adoc 
b/docs/modules/ROOT/pages/reference/extensions/jms.adoc
index e8669825a5..67dce11095 100644
--- a/docs/modules/ROOT/pages/reference/extensions/jms.adoc
+++ b/docs/modules/ROOT/pages/reference/extensions/jms.adoc
@@ -59,10 +59,11 @@ you must ensure that the `camel-quarkus-jaxp` extension is 
present on the classp
 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.
 
-[id="extensions-jms-usage-pooling-and-xa-integrate-support"]
-=== Pooling and XA integrate support
+[id="extensions-jms-usage-support-for-connection-pooling-and-x-open-xa-distributed-transactions"]
+=== Support for Connection pooling and X/Open XA distributed transactions
 
-You can use the `quarkus-pooled-jms` extension to get pooling and XA integrate 
support for JMS connections. Refer to the 
https://quarkiverse.github.io/quarkiverse-docs/quarkus-pooled-jms/dev/index.html[quarkus-pooled-jms]
 extension documentation for more information. Currently, it only works with 
`quarkus-artemis-jms` extension. Just add these two dependencies to your 
`pom.xml`:
+You can use the `quarkus-pooled-jms` extension to get pooling and XA support 
for JMS connections. Refer to the 
https://quarkiverse.github.io/quarkiverse-docs/quarkus-pooled-jms/dev/index.html[quarkus-pooled-jms]
 extension documentation for more information.
+Currently, it only works with `quarkus-artemis-jms` extension. Just add these 
two dependencies to your `pom.xml`:
 [source,xml]
 ----
 <dependency>
@@ -75,7 +76,9 @@ You can use the `quarkus-pooled-jms` extension to get pooling 
and XA integrate s
 </dependency>
 ----
 
-Pooling is default enabled and for XA integrate support, you need to add the 
following configuration to your `application.properties`:
+Note that pooling is enabled by default.
+
+To enable XA, you need to add the following configuration to your 
`application.properties`:
 [source,properties]
 ----
 quarkus.pooled-jms.xa.enabled=true
diff --git a/extensions/jms/runtime/src/main/doc/usage.adoc 
b/extensions/jms/runtime/src/main/doc/usage.adoc
index 788a0f50a3..4517ad3b87 100644
--- a/extensions/jms/runtime/src/main/doc/usage.adoc
+++ b/extensions/jms/runtime/src/main/doc/usage.adoc
@@ -8,9 +8,10 @@ you must ensure that the `camel-quarkus-jaxp` extension is 
present on the classp
 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.
 
-=== Pooling and XA integrate support
+=== Support for Connection pooling and X/Open XA distributed transactions
 
-You can use the `quarkus-pooled-jms` extension to get pooling and XA integrate 
support for JMS connections. Refer to the 
https://quarkiverse.github.io/quarkiverse-docs/quarkus-pooled-jms/dev/index.html[quarkus-pooled-jms]
 extension documentation for more information. Currently, it only works with 
`quarkus-artemis-jms` extension. Just add these two dependencies to your 
`pom.xml`:
+You can use the `quarkus-pooled-jms` extension to get pooling and XA support 
for JMS connections. Refer to the 
https://quarkiverse.github.io/quarkiverse-docs/quarkus-pooled-jms/dev/index.html[quarkus-pooled-jms]
 extension documentation for more information.
+Currently, it only works with `quarkus-artemis-jms` extension. Just add these 
two dependencies to your `pom.xml`:
 [source,xml]
 ----
 <dependency>
@@ -23,7 +24,9 @@ You can use the `quarkus-pooled-jms` extension to get pooling 
and XA integrate s
 </dependency>
 ----
 
-Pooling is default enabled and for XA integrate support, you need to add the 
following configuration to your `application.properties`:
+Note that pooling is enabled by default.
+
+To enable XA, you need to add the following configuration to your 
`application.properties`:
 [source,properties]
 ----
 quarkus.pooled-jms.xa.enabled=true

Reply via email to