fix: EXPOSED-593 Rollback ExposedSQLException when use SpringTransactionManager

[FullOfOrange]

Description

Summary of the change:

• Add ExposedSpringTransactionAttributeSource to fix transaction not rollback when an ExposedSQLException thrown when using SpringTransactionManager.

• Added @bean settings to spring-boot-starter

Detailed description:

• What: Introduces ExposedSpringTransactionAttributeSource. This is an implementation of TransactionAttributeSource, a class for setting attributes on a transaction, and a class for adding ExposedSQLException as a rollback rule.
• Why: Spring only rollback UncheckedExceptions when using the @Transactional annotation, but ExposedSQLException is a CheckedException and cannot be rolled back. This makes the behavior different from the default exposed transaction, and want to fix it.
• How:
  • Implemented ExposedSpringTransactionAttributeSource to allow you to add an exception to the rollback rule.
    • If you use spring-boot-starter, it will automatically register the bean for you.
    • If you set it up yourself, you can register the ExposedSpringTransactionAttributeSource as a bean yourself and use it. (set up same as spring-boot-starter).

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

• ExposedSQLException is not an runtime exception for Spring #1419

[bog-walk]

Thanks for working on this PR @FullOfOrange

Just a request to edit one of the KDocs.

Please also consider rebasing from main.

[bog-walk]

Correct me if you're actually seeing something else in the IDE, but this format (lines 78-79) will cause the lines to be ignored and not appear as part of the KDocs that show when the function is hovered over in the IDE. The KDocs attempts to resolve @Primary as a block tag, but it is not valid so it is ignored entirely.

Please quote the annotation in either backticks or single quotation marks to make it appear properly in KDocs.

[FullOfOrange]

Oh, thank you for your review! I’ve applied your feedback.

[e5l]

Hey @FullOfOrange, thank you for the PR! LGTM