kutouziUk commented on issue #34556: URL: https://github.com/apache/shardingsphere/issues/34556#issuecomment-2633212782
> * If you mean the `org.apache.seata.spring.annotation.GlobalTransactional` annotation, that annotation is actually only processed by `org.apache.seata.spring.annotation.GlobalTransactionScanner`, and the related classes are actually only valid for Spring Framework. The metadata scanning of shardingsphere actually bypasses all spring-related things.如果你指的是 `org.apache.seata.spring.annotation.GlobalTransactional` Comments，那么该 Comments 实际上只由 `org.apache.seata.spring.annotation.GlobalTransactionScanner` 处理，并且相关类实际上仅对 Spring Framework 有效。shardingsphere 的元数据扫描实际上绕过了所有与 Spring 相关的事情。 > * I am not sure how [建议：关于 seata-integration-tx-api 下的 GlobalTransactional 注解命名问题 incubator-seata#6951](https://github.com/apache/incubator-seata/issues/6951) will be resolved in the end. The logic of re-implementing `org.apache.seata.spring.annotation.GlobalTransactionScanner` on the shardingsphere side seems a bit strange. The public java api of shardingsphere is basically disguised as a normal java datasource.我不确定最终会如何 [建议：关于 seata-integration-tx-api 下的 GlobalTransactional 注解命名问题 incubator-seata#6951](https://github.com/apache/incubator-seata/issues/6951) 解决。在 shardingsphere 端重新实现 `org.apache.seata.spring.annotation.GlobalTransactionScanner` 的逻辑似乎有点奇怪。shardingsphere 的公共 java api 基本都是伪装成普通的 java 数据源。 @GlobalTransactional is just an example and is not intended to implement its logic on the shardingjdbc side. What I want to say is that after configuring TRANSACTION=BASE, all data sources are brokered globally by Seata. In the case of a single data source, the full Seata AT process could not have been executed because using external components would have introduced more risk, and it would have been better to commit the transaction more simply and quickly, without the need to involve Seata's two-stage commit. Seata's two-phase commit is performed only when distributed transactions are involved. I just want to consult whether there is such a solution in shardingjdbc, but I don't know. If not, I will use the current global proxy. -- 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: notifications-unsubscr...@shardingsphere.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
