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

Allow usage of specific serializers for the JpaDLQ #2486

Merged
merged 2 commits into from Nov 15, 2022

Conversation

CodeDrivenMitch
Copy link
Member

In some cases, differentiation is wanted when serializing a dead letter to the database. This PR allows users to configure an event serializer, and a generic serializer.

The event serializer is used for serialization of the event payload, event metadata, and diagnostics of the Dead letter.
The generic serialize is used for the serialization of the tracking token.

The builder still has the serializer() method and I have decided not to deprecate it. In a lot of cases, setting one serializer for both types is enough.

Closing #2485

@CodeDrivenMitch CodeDrivenMitch added Type: Enhancement Use to signal an issue enhances an already existing feature of the project. Priority 1: Must Highest priority. A release cannot be made if this issue isn’t resolved. labels Nov 15, 2022
@CodeDrivenMitch CodeDrivenMitch added this to the Release 4.6.3 milestone Nov 15, 2022
@CodeDrivenMitch CodeDrivenMitch requested a review from a team November 15, 2022 12:36
@CodeDrivenMitch CodeDrivenMitch self-assigned this Nov 15, 2022
@CodeDrivenMitch CodeDrivenMitch requested review from gklijs and smcvb and removed request for a team November 15, 2022 12:36
@CodeDrivenMitch CodeDrivenMitch linked an issue Nov 15, 2022 that may be closed by this pull request
Copy link
Contributor

@gklijs gklijs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 👍

@smcvb smcvb added the Status: In Progress Use to signal this issue is actively worked on. label Nov 15, 2022
Copy link
Member

@smcvb smcvb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two minor JavaDoc comments. Otherwise, this looks good.

Co-authored-by: Steven van Beelen <steven.vanbeelen@axoniq.io>
@CodeDrivenMitch CodeDrivenMitch merged commit bd0a0e9 into axon-4.6.x Nov 15, 2022
@CodeDrivenMitch CodeDrivenMitch added Status: Resolved Use to signal that work on this issue is done. and removed Status: In Progress Use to signal this issue is actively worked on. labels Nov 15, 2022
@CodeDrivenMitch CodeDrivenMitch deleted the feature/2485-dlq-serializers-expansion branch November 15, 2022 14:44
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

Successfully merging this pull request may close these issues.

DeadLetterQueue uses wrong Serializer to (de)serialize Tokens
3 participants