Replies: 2 comments
-
If you publish an event and it fails to store in the data source, it is because, your lacking to consume / listen the published event. To test this kindly, create an @ApplicationModuleListener that perhaps even that just logs out a message, the published event shall be saved in the data source |
Beta Was this translation helpful? Give feedback.
0 replies
-
Here are the SQL scripts you can use to initialize your own database schema: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am using modulith and Spring Application Events in my project and some listeners are going to be calling a flaky API. Since we expect some publications to fail, we wanted to take advantage of republishing failed events. However, in documentation, I don’t see WHERE failed events are persisted.
“IncompleteEventPublications — This interface allows accessing all incomplete event publications to resubmit either the ones matching a given predicate or older than a given Duration relative to the original publishing date.
Event Publication Completion
Event publications are marked as completed when a transactional or @ApplicationModuleListener execution completes successfully. By default, the completion is registered by …”
This comes from https://docs.spring.io/spring-modulith/reference/events.html
I believe this is missing information from the doc.
Beta Was this translation helpful? Give feedback.
All reactions