-
Notifications
You must be signed in to change notification settings - Fork 98
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
[663] Yasson 3.0.3 - Serialization of a Map fails if the key is of a type implemented as SupportedMapKey and using a csutom Serializer #664
base: master
Are you sure you want to change the base?
Conversation
@Verdent please provide a link tot eh ECA to sign... |
src/main/java/org/eclipse/yasson/internal/serializer/MapSerializer.java
Outdated
Show resolved
Hide resolved
src/main/java/org/eclipse/yasson/internal/serializer/MapSerializer.java
Outdated
Show resolved
Hide resolved
src/main/java/org/eclipse/yasson/internal/serializer/MapSerializer.java
Outdated
Show resolved
Hide resolved
* @return whether a custom JsonSerializer for the type is available | ||
*/ | ||
public static boolean hasCustomJsonbSerializer(Class<?> clazz, JsonbContext jsonbContext) { | ||
return jsonbContext.getComponentMatcher().getSerializerBinding(clazz, null).isPresent(); |
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.
Should we be passing the propertyCustomization
parameter from SerializationModelCreator.createMapSerializer()
as the null
parameter here?
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.
Hm, not sure here... This method is only to determine if there's a custom Serializer at all...
Using the custom JsonbSerializer even when serializing an already supported Map key
75264e2
to
873bfe4
Compare
rebased on current 'master' incorporated review comments
This fixes issue #663