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

[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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

jbaesner
Copy link

This fixes issue #663

@jbaesner
Copy link
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
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
Author

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

@jbaesner
Copy link
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
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
Contributor

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
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
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