-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Fix reflection registration issue with Jackson's @JsonSerialize & @JsonDeserialize #17049
Conversation
…onDeserialize This is a follow up to PR quarkusio#12387. It registers the rest of the “using” options (`keyUsing`, `contentUsing`, `nullsUsing`) for both `@JsonSerialize` and `@JsonDeserialize`
// the Deserializers are constructed internally by Jackson using a no-args constructor | ||
reflectiveClass | ||
.produce(new ReflectiveClassBuildItem(false, false, contentUsingValue.asClass().name().toString())); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we need to also consider all the others (converters, as...)? Not sure about as
but the 2 converter properties look like something we should take into account.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering the same. I can make another PR and add them.
// the Deserializers are constructed internally by Jackson using a no-args constructor | ||
reflectiveClass | ||
.produce(new ReflectiveClassBuildItem(false, false, nullsUsingValue.asClass().name().toString())); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question here.
This is a follow up to PR #12387.
It registers the rest of the “using” options (
keyUsing
,contentUsing
,nullsUsing
) for both@JsonSerialize
and@JsonDeserialize