Lifecycle CDI Event
A pull request for this has already been merged.
- #876 by @gavinking — merged
- Dominant language
- Java
- Stars
- 150
- Forks
- 37
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 34
Description
Like the JPA event listener and do side effect by annotations `@Save`, `@Merge`, etc(till now I do not know well about the purpose of these annotations).
Spring Data provides a collection of `XXXCallback` when converting/saving/updating/delete an entity object.
In Jakarta Data, we can introduce CDI Event instead, make it compatible with all implementation modules.
It is more freely for developers.
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 by reviewing the issue's references to JPA event listeners, @Save/@Merge annotations, Spring Data XXXCallback, and CDI Event. Clarify the intended lifecycle events and how CDI events would remain compatible across implementation modules. Done should be a decided, specified approach rather than an open-ended comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100