From 214e02cab0bad7e2706daafda54ac7994f0796dc Mon Sep 17 00:00:00 2001
From: Marco Bungart <marco.bungart@googlemail.com>
Date: Wed, 20 Sep 2023 21:17:38 +0200
Subject: [PATCH] Docs: Reword XA-section

---
 docs/modules/ROOT/pages/index.adoc | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc
index e421c25c..5fb243ef 100644
--- a/docs/modules/ROOT/pages/index.adoc
+++ b/docs/modules/ROOT/pages/index.adoc
@@ -27,9 +27,9 @@ a|
 a|
 latest `3.0.x`
 a|
-(upcoming) `3.3.x`
+`3.3.x`
 a|
-(upcoming) `3.1.x`
+`3.1.x`
 |===
 
 .LTS Support
@@ -262,10 +262,11 @@ TIP: If we want to configure a connection solely through the implicit environmen
 
 Please do not try to configure a configuration purely through environment variables, without having any indication of its presence in the application's configuration file. We specifically rely on the presence of some configuration fragment at build-time to detect configurations.
 
-== XA Transactions
-XA Transactions  must be activated on a per-configuration basis, they are not enabled by default.
+== XA-capable Connection Factories
 
-To activate XA transactions, we can set `quarkus.artemis.xa-enabled` / `quarkus.artemis."named-configuration".xa-enabled` to *true*.
+To get XA-capable connection factories, we can set `quarkus.artemis.xa-enabled` / `quarkus.artemis."named-configuration".xa-enabled` to *true*. We can then inject the corresponding bean as `XAConnectionFactory`.
+
+To use XA transactions and integrate with a transaction manager, we recommend using the link:https://github.com/quarkiverse/quarkus-pooled-jms[quarkus-pooled-jms quarkiverse extension].
 
 == URL as optional configuration
 The `url` configuration property is optional. But in general, without a `url` property, we cannot create a connection. In case of tests with embedded resources or devservices, the corresponding annotation/service injects a url. But if  the application starts up and no `url` property is found, the creation of the bean will throw a `RuntimeException` with a corresponding error message. Notice that this will happen when the bean is created. If the bean is never used (and thus never created), the exception will not occur.