Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide infrastructure for replaying events #25

Closed
abuijze opened this issue Jan 2, 2012 · 0 comments
Closed

Provide infrastructure for replaying events #25

abuijze opened this issue Jan 2, 2012 · 0 comments
Assignees
Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
Milestone

Comments

@abuijze
Copy link
Member

abuijze commented Jan 2, 2012

Event Listeners should be able to reconstruct themselves using events stored in the Event Store.

To accomplish this, event listeners can implement an interface, which is given a DomainEventStream from which events can be pulled. Alternatively, annotation support can be provided using @BeforeReplay and @AfterReplay (or similar) annotations to express the functionality needed before replaying starts and when it is completed. These methods allow the listener to clear tables and commit a transaction.

@abuijze abuijze closed this as completed Dec 30, 2016
@smcvb smcvb added Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. labels Jul 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. Status: Resolved Use to signal that work on this issue is done. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
Projects
None yet
Development

No branches or pull requests

2 participants