[#1035] Utilize TransactionManager on append events operation #1043
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request ensure that the
JpaEventStorageEngine
uses theTransactionManager
to perform theappendEvents(List<EventMessage>, Serializer)
call in a Transaction, always.Typically, this transaction is started by the
CommandGateway
is that's the starting point of entering an Aggregate/External Command Handler, and applying events as a result of that.However, if somebody would want to publish events directly when utilizing the
JpaEventStorageEngine
, then that would form an issue from a Transaction perspective.This pull request resolve #1035