Spring/spring-modulith
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

GH-288 - Clarify event republication behavior on restart.

Browse Source
This commit is contained in:
Oliver Drotbohm
2023-09-04 09:46:33 +02:00
parent 28fcdf1f1e
commit 3aa6a12b21
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/docs/asciidoc/40-events.adoc
View File

@@ -117,7 +117,9 @@ image::event-publication-registry-start.png[]
Each transactional event listener is wrapped into an aspect that marks that log entry as completed if the execution of the listener succeeds.
In case the listener fails, the log entry stays untouched so that retry mechanisms can be deployed depending on the application's needs.
By default, all incomplete event publications are resubmitted at application startup.
Automatic republication on application restart can be enabled by setting the `spring.modulith.republish-outstanding-events-on-restart` property to `true`.
Note, that this is only recommended for single-instance application deployments.
For a more flexible arrangement, `EventPublicationRegistry` exposes a method `….findIncompletePublications()` that can be called from user code.
.The transactional event listener arrangement after execution
image::event-publication-registry-end.png[]