zhfeng commented on code in PR #14130:
URL: https://github.com/apache/shardingsphere/pull/14130#discussion_r907986207
##########
docs/document/content/features/transaction/use-norms/xa.en.md:
##########
@@ -13,3 +13,101 @@ weight = 2
## Unsupported
* Recover committing and rolling back in other machines after the service is
down.
+
+## XA Transaction managed by XA Statement
Review Comment:
I think the difference between `XAMANUAL` and `XA` is that users can
contronl the XA transaction by themselves in `XAMANUAL` and `sharding-proxy`
contronls XA transction in `XA`.
I think the motivation to add this transaction type is that users want to do
the XA operations by themselves in such case like involving in two or more
resources in a transacion, e.g.
```
tx.begin();
jms.send("/queue/test", "messages"); // send to a message broker
jdbc.update("insert into db_test"); // insert into database through the proxy
tx.commit();
```
And yeah, in this scenario, users should be responsible to the transaction
operations. `sharding-proxy` just bypass all of the XA related statments to the
backend databases;
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
