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

Use the same objectMapper everwhere #6

Closed
ptitFicus opened this issue Nov 25, 2020 · 0 comments · Fixed by #7
Closed

Use the same objectMapper everwhere #6

ptitFicus opened this issue Nov 25, 2020 · 0 comments · Fixed by #7
Assignees

Comments

@ptitFicus
Copy link
Member

A different ObjectMapper is used to publish events in Kafka at first try and to write events in database.
This can cause bugs when republishing events in kafka if first publication failed, since the two are not compatible, for instance on vavr lists.

I think the best way to do it would be to instantiate and use some kind of singleton ObjectMapper, that is exposed for modification.

@ptitFicus ptitFicus self-assigned this Nov 25, 2020
This was referenced Nov 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant