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

Aggregate event publishing should prefer parameters instead of returned values from save(…) [DATACMNS-1163] #1604

Closed
spring-projects-issues opened this issue Sep 20, 2017 · 0 comments
Assignees
Milestone

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Sep 20, 2017

Oliver Drotbohm opened DATACMNS-1163 and commented

For some persistence technologies, save(…) methods might return a completely different instance of the object handed to it in the method. This might cause the returned instance not containing the events originally held so that the event publishing mechanism fails to find them. We should rather use the instances that are handed into the method for event inspection


Affects: 2.0 RC3 (Kay), 1.13.7 (Ingalls SR7)

Backported to: 1.13.8 (Ingalls SR8)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants