Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move ChainedTransactionManager from spring-data commons to spring-tx [SPR-13735] #18308

Closed
spring-projects-issues opened this issue Nov 29, 2015 · 2 comments
Labels
in: data status: declined type: enhancement

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Nov 29, 2015

Attila Király opened SPR-13735 and commented

Spring-data common has a hidden gem: ChainedTransactionManager.
It is not mentioned in the reference documentation only in javadoc.
There is a good blog entry about it which describes why it is useful.

ChainedTransactionManager is in a package which doesn't have any dependency on anything else in spring-data. Basically it only depends on org.springframework.transaction from spring-tx.

Considering that it is a pretty general functionality, could it be moved (and documented) into spring-tx itself?


Affects: 4.2.3, 5.0 M4

Issue Links:

  • #8524 Provide a "best efforts" 1PC transaction manager out of the box

Referenced from: pull request #1324

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented May 26, 2016

Attila Király commented

Related jiras: #8524 and DATAGRAPH-256

@snicoll
Copy link
Member

@snicoll snicoll commented Nov 24, 2021

With ChainedTransactionManager being deprecated in Spring Data, we have no intention to move this feature in the core framework. Thanks for the suggestion, in any case.

@snicoll snicoll closed this as completed Nov 24, 2021
@snicoll snicoll added the status: declined label Nov 24, 2021
@snicoll snicoll removed this from the General Backlog milestone Nov 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data status: declined type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants