Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Integrate event publication log, formerly known as Spring Domain Events #121

Closed
odrotbohm opened this issue Sep 16, 2020 · 0 comments
Closed
Assignees
Labels
type: enhancement New feature or request
Milestone

Comments

@odrotbohm
Copy link
Collaborator

See https://github.com/odrotbohm/spring-domain-events.

@odrotbohm odrotbohm added the type: enhancement New feature or request label Sep 16, 2020
@odrotbohm odrotbohm added this to the 1.1 M1 milestone Sep 16, 2020
@odrotbohm odrotbohm self-assigned this Sep 16, 2020
odrotbohm added a commit that referenced this issue Sep 16, 2020
Tweaked artifact identifiers and package names.

Tweaked dependency setup to avoid referring to Spring Boot artifacts and rather resort to plain Spring dependencies and only the Spring Boo Tests starter.
odrotbohm added a commit that referenced this issue Oct 23, 2020
Upgrade the events module to Spring 5.3 snapshots to simplify the implementation using the newly introduced APIs.
odrotbohm added a commit that referenced this issue Nov 13, 2020
Upgrade the events module to Spring 5.3 snapshots to simplify the implementation using the newly introduced APIs.
odrotbohm added a commit that referenced this issue Nov 27, 2020
JpaEventPublicationRegistry now keeps an explicit reference to EntityManager to prevent the EntityManagerFactory from being shut down before it can actually execute it's final logging operations.

This is a temporary fix, shouldn't be needed and needs to be investigated further.
odrotbohm added a commit that referenced this issue Nov 27, 2020
…istry.

We now use explicit bean factory method parameters for the dependencies for JpaEventPublicationRegistry to be created. This is needed to let Spring Framework detect the logical bean dependency between the registry and the repository to properly shut them down in the correct order.

The previously used arrangement via configuration class constructor arguments hides that dependency and potentially already shuts down the repository or downstream beans which then will cause the shutdown hook in JpaEventPublicationRegistry itself to fail as it still needs to trigger a repository query in that.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant