liuyangming opened a new issue #2902: When shardingjdbc is integrated with spring, it‘s not compatible with the declarative transactions. URL: https://github.com/apache/incubator-shardingsphere/issues/2902 ## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/incubator-shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response **more than 7 days** and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? 4.0.0-RC2-SNAPSHOT ### Which project did you use? Sharding-JDBC or Sharding-Proxy? Sharding-JDBC ### Expected behavior In the scenario of declarative transaction, when the service throws a RuntimeException, the transaction should be rolled back. ### Actual behavior In fact, the transaction was committed. ### Reason analyze (If you can) ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. Please refer to the description of README.md in this project: [shardingjdbc-sample](https://github.com/liuyangming/shardingjdbc-sample) ### Example codes for reproduce this issue (such as a github link). [https://github.com/liuyangming/shardingjdbc-sample](https://github.com/liuyangming/shardingjdbc-sample)
---------------------------------------------------------------- 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] With regards, Apache Git Services
