spring-projects / spring-projects/spring-data-commons
Introduce standardized interfaces for published application events
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 838
- Forks
- 730
- PR merge metrics
- No merged PRs in 30d
Description
A possible enhancement to functionality detailed in the docs at https://docs.spring.io/spring-data/data-jpa/reference/data-commons/repositories/core-domain-events.html.
Any time, say, the save method is called (from CrudRepository), standard Spring created events (like Spring Data REST's BeforeSaveEvent and AfterSaveEvent) would be published. This would allow developers to create custom event handlers for standard lifecycle events without having to register custom events on those entities.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the core-domain-events documentation and the CrudRepository save method mentioned in the issue. Compare the existing Spring Data REST BeforeSaveEvent and AfterSaveEvent concepts, then determine the interface and lifecycle scope needed for standardized published events. Done means the intended standard events can be handled without custom entity events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100