Nikita-tech-writer commented on a change in pull request #8948:
URL: https://github.com/apache/ignite/pull/8948#discussion_r604023720



##########
File path: docs/_docs/extensions-and-integrations/spring/spring-tx.adoc
##########
@@ -0,0 +1,471 @@
+// Licensed to the Apache Software Foundation (ASF) under one or more
+// contributor license agreements.  See the NOTICE file distributed with
+// this work for additional information regarding copyright ownership.
+// The ASF licenses this file to You under the Apache License, Version 2.0
+// (the "License"); you may not use this file except in compliance with
+// the License.  You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+= Apache Ignite With Spring Transactions
+
+== Overview
+
+http://docs.spring.io/spring/docs/current/spring-framework-reference/html/transaction.html[Spring
 Transactions, window="_blank"]
+abstraction allows you to use declarative transaction management to 
concentrate on business logic rather than
+transaction life-cycle.
+
+Apache Ignite provides an extension - `ignite-spring-tx-ext` - that allows you 
to manage
+https://ignite.apache.org/docs/latest/key-value-api/transactions#performing-transactions[Apache
 Ignite Transactions, window="_blank"]
+through Spring Transactions abstraction. The mentioned integration is achieved 
by providing implementations of the Spring
+Transactions `TransactionManager` interface. There are two such 
implementations: `SpringTransactionManager` and
+`IgniteClientSpringTransactionManager`, which use Apache Ignite node or Apache 
Ignite thin client to connect to an
+Apache Ignite cluster and manage Apache Ignite transactions, respectively.
+
+To enable declarative transaction management in your Spring application, you 
need to create and configure
+`SpringTransactionManager` or `IgniteClientSpringTransactionManager` bean in 
the Spring application context. The choice
+of implementation depends on your preferable way to access the Apache Ignite 
cluster.
+
+== Maven Configuration
+
+If you are using Maven to manage dependencies in your project, you can add 
Spring Transactions extension dependencies to
+an application's `pom.xml` file like this:
+
+[NOTE]
+====
+For Apache Ignite versions earlier than `2.11.0`, the `ignite-spring-tx-ext` 
dependency must be added to
+classpath before `ignite-spring`, due to duplication of Spring Transactions 
integration classes. If you are using Maven
+to manage dependencies, it just needs to place `ignite-spring-tx-ext` before 
`ignite-spring` dependency in an
+application's `pom.xml` file.

Review comment:
       ```suggestion
   For Apache Ignite versions earlier than `2.11.0`, the `ignite-spring-tx-ext` 
dependency must be added to classpath before `ignite-spring`, due to 
duplication of Spring Transactions integration classes. If you are using Maven 
to manage dependencies, place `ignite-spring-tx-ext` before the `ignite-spring` 
dependency in the application's `pom.xml` file.
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to