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

Allow some domain events to be processed within the current transaction and others to be processed after #29

Closed
barsifedron opened this issue Nov 20, 2021 · 0 comments · Fixed by #33 or #34
Assignees
Labels
enhancement New feature or request

Comments

@barsifedron
Copy link
Owner

One domain event might trigger many event handlers (ie: one handler creates
activity logs and the other sends emails or updates a counter). If handler1
and handler2 both listen to the same event, we might want handler1 to run
within the SAME jpa transaction as the caller (default behavior) but we might
also want handler2 to wait for the current transaction to be committed before
running (failure to send an email should not usually roll back successful
changes for example).

@barsifedron barsifedron self-assigned this May 13, 2024
@barsifedron barsifedron added the enhancement New feature or request label Sep 9, 2024
@barsifedron barsifedron reopened this Sep 10, 2024
@barsifedron barsifedron linked a pull request Sep 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
1 participant