Skip to content

[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

Merged
Verdent merged 2 commits intoeclipse-ee4j:masterfrom
jbaesner:issue663
Jul 11, 2025
Merged

Conversation

@jbaesner
Copy link
Copy Markdown
Contributor

This fixes issue #663

@jbaesner
Copy link
Copy Markdown
Contributor Author

@m0mus @Verdent the same customer of JBoss EAP facing the issue from PR #599 needs this issue fixed as well.

Could one of you look at this by chance? Thanks in advance.

@Verdent
Copy link
Copy Markdown
Member

Verdent commented Mar 13, 2025

Hello @jbaesner , Issue #599 will be fixed by this: #661
I posted my review there.

Thank you for your contribution and please, do not forget to sign the ECA.

@jbaesner
Copy link
Copy Markdown
Contributor Author

@Verdent please provide a link tot eh ECA to sign...

@jbaesner
Copy link
Copy Markdown
Contributor Author

Hello @jbaesner , Issue #599 will be fixed by this: #661 I posted my review there.

Thank you for your contribution and please, do not forget to sign the ECA.

I have now signed the ECA, can this change get merged?

@jbaesner
Copy link
Copy Markdown
Contributor Author

jbaesner commented Apr 9, 2025

@Verdent is there anything missing to get this PR merged? As I mentioned earlier a customer of JBoss EAP who is facing the issue from PR #599 needs this issue fixed as well, so it would be great if we could get this merged...

* @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();
Copy link
Copy Markdown
Member

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?

Copy link
Copy Markdown
Contributor Author

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
@jbaesner jbaesner force-pushed the issue663 branch 2 times, most recently from 75264e2 to 873bfe4 Compare April 11, 2025 06:15
rebased on current 'master'
incorporated review comments
@jamezp
Copy link
Copy Markdown
Member

jamezp commented Apr 14, 2025

This looks good to me. What do you think @Verdent?

@jbaesner
Copy link
Copy Markdown
Contributor Author

@Verdent I see the workflow needs an approval from a maintainer. Is there something missing here? What need to be done to get this PR merged?

@jbaesner
Copy link
Copy Markdown
Contributor Author

jbaesner commented Jun 2, 2025

@m0mus @Verdent, is there a chance to get this PR for issue #663 merged and included in a new release, as we have a customer on JBoss EAP 8 facing this issue and we need to have yasson updated to resolve the issue. Thank you very much.

@Verdent Verdent merged commit d60c869 into eclipse-ee4j:master Jul 11, 2025
1 check passed
@Verdent
Copy link
Copy Markdown
Member

Verdent commented Jul 11, 2025

Thank you for your contribution! And sorry for it to take so long to get in :-)

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 this pull request may close these issues.

3 participants