This is an automated email from the ASF dual-hosted git repository.
dspavlov pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ignite.git
The following commit(s) were added to refs/heads/master by this push:
new 6b70c742614 IGNITE-28887 Document Spring 6 JTA migration (#13364)
6b70c742614 is described below
commit 6b70c7426143f8a23eea93ff77f3e1a304abcd03
Author: ignitetcbot <[email protected]>
AuthorDate: Tue Jul 14 13:36:36 2026 +0300
IGNITE-28887 Document Spring 6 JTA migration (#13364)
Codex co-authored-by: Ignite TC Bot <[email protected]>
---
docs/_docs/extensions-and-integrations/spring/spring-tx.adoc | 7 +++++++
docs/_docs/setup.adoc | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
diff --git a/docs/_docs/extensions-and-integrations/spring/spring-tx.adoc
b/docs/_docs/extensions-and-integrations/spring/spring-tx.adoc
index 442b03d834f..d6e6d0edbfc 100644
--- a/docs/_docs/extensions-and-integrations/spring/spring-tx.adoc
+++ b/docs/_docs/extensions-and-integrations/spring/spring-tx.adoc
@@ -155,6 +155,13 @@ of the Apache Ignite and Spring.
| 1.0.0 | All versions since 2.11.0 | All versions since 4.3.0
|===
+[NOTE]
+====
+Starting with Apache Ignite 2.19, Spring integration is based on Spring
Framework 6 and Jakarta EE APIs.
+If your application uses `ignite-jta` transaction manager lookup classes,
compile custom lookup code against
+`jakarta.transaction.TransactionManager` instead of the legacy
`javax.transaction.TransactionManager`.
+====
+
== Apache Ignite Node Transaction Manager Configuration
This chapter shows how to set up `SpringTransactionManager` that relies on
Apache Ignite node to connect to the cluster
and to manage transactions. The configuration consists of two steps -
diff --git a/docs/_docs/setup.adoc b/docs/_docs/setup.adoc
index e3178beb778..8cdb8bcc9e0 100644
--- a/docs/_docs/setup.adoc
+++ b/docs/_docs/setup.adoc
@@ -208,7 +208,7 @@ The following modules are available:
|ignite-jcl |Support for the Jakarta Common Logging (JCL) framework.
-|ignite-jta |Integration of Ignite transactions with JTA.
+|ignite-jta |Integration of Ignite transactions with JTA. Starting with Apache
Ignite 2.19, custom JTA integration code must use Jakarta Transaction API
classes, such as `jakarta.transaction.TransactionManager`.
|ignite-kafka | Ignite Kafka Streamer provides capability to stream data from
Kafka to Ignite caches.
