TransactionalEventListener seperate phase AFTER_COMPLETION and AFTER_COMMIT for a group of events [SPR-15323] #19886
Labels
in: data
Issues in data modules (jdbc, orm, oxm, tx)
status: declined
A suggestion or change that we don't feel we should currently apply
type: enhancement
A general enhancement
Mark Czubin opened SPR-15323 and commented
Currently the TransactionSynchronizationEventAdapter will handle both
TransactionPhase.AFTER_COMPLETION
andTransactionPhase.AFTER_COMMIT
in the same callback function:
TransactionSynchronization::afterCompletion
.I would expect
TransactionPhase.AFTER_COMMIT
to be handled insideTransactionSynchronization::afterCommit
.So all events will first be handled in
TransactionPhase.AFTER_COMMIT
and afterwards all events will be handled in
TransactionPhase.AFTER_COMPLETION
.Now they are handled at the same time.
Affects: 4.3.7
The text was updated successfully, but these errors were encountered: