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

[#1035] Utilize TransactionManager on append events operation #1043

Merged
merged 1 commit into from Mar 26, 2019

Conversation

smcvb
Copy link
Member

@smcvb smcvb commented Mar 26, 2019

This pull request ensure that the JpaEventStorageEngine uses the TransactionManager to perform the appendEvents(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

The JpaEventStorageEngine should ensure that an appendEvents call is
always performed within a transaction. To that end, the
TransactionManager#executeInTransction(Runnable) function should be
utilized to wrap the appending of events in a transaction

#1035
@smcvb smcvb added Type: Bug Use to signal issues that describe a bug within the system. Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: In Progress Use to signal this issue is actively worked on. labels Mar 26, 2019
@smcvb smcvb added this to the Release 4.1.1 milestone Mar 26, 2019
@smcvb smcvb self-assigned this Mar 26, 2019
@smcvb smcvb changed the base branch from master to axon-4.1.x March 26, 2019 15:34
@smcvb smcvb merged commit 5aa411d into axon-4.1.x Mar 26, 2019
@smcvb smcvb deleted the bug/1035 branch March 26, 2019 16:21
@smcvb smcvb added Status: Resolved Use to signal that work on this issue is done. and removed Status: In Progress Use to signal this issue is actively worked on. labels Mar 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Bug Use to signal issues that describe a bug within the system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant