linghengqian commented on issue #29712: URL: https://github.com/apache/shardingsphere/issues/29712#issuecomment-1951062127
> > * I believe this is essentially a duplicate of [SpringCloud+Seata1.5.2+ShardingSphereJDBC5.2.1 SeataATShardingSphereTransactionManager.commit throw null exception #22356 (comment)](https://github.com/apache/shardingsphere/issues/22356#issuecomment-1948463141) , and the use of annotations within `io.seata:seata-spring-boot-starter` should be avoided, including `io.seata.spring.annotation.GlobalTransactional`. > > * I believe this issue involves adjustments to the Spring Boot Starter side of Seata. > > 我用新提交的文档说明里面的依赖跑不起来, 我主要用这俩 > > ``` > <dependency> > <groupId>com.alibaba.cloud</groupId> > <artifactId>spring-cloud-starter-alibaba-seata</artifactId> > <version>2022.0.0.0</version> > </dependency> > > <dependency> > <groupId>org.apache.shardingsphere</groupId> > <artifactId>shardingsphere-transaction-base-seata-at</artifactId> > <version>5.4.1</version> > </dependency> > ``` > > 但是仍然有问题, 似乎单个服务没有问题, 多个服务之间没有事务组的概念, 每个服务都是单独的全局事务, 都会独自提交事务; 不知道这边有完整的demo吗? @linghengqian - This seems a bit difficult to verify, so let me modify the seata side of the example to test it. The problem involved here is that currently all unit tests assume that only a single transaction group is used. -- 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]
