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
Serializer for class 'ArrayList' is not found. #28096
Comments
Can you provide a small reproducer? |
/cc @evanchooly, @geoand |
As Guillaume mentions, a reproducer is essential here. |
Thanks for the super fast response! Interesting... we get it every time in our app... but are having trouble reproducing it with a fresh hello world... this might take a moment. Otherwise, in the case of Lists, is https://github.com/quarkusio/quarkus/blob/main/extensions/resteasy-reactive/quarkus-resteasy-reactive-kotlin-serialization/runtime/src/main/kotlin/io/quarkus/kotlin/serialization/KotlinSerializationMessageBodyWriter.kt still used to serialize the data? |
Yeah, that should be coming into play |
Ok, we are 1 step closer. It all comes down to the KotlinSerializationMessageBodyWriter.kt. On the Reproducer App, So 2 questions:
|
Seems like some of the tests are failing, so there is more I need to look into |
Ok, found the culprit. When adding "io.quarkus:quarkus-smallrye-opentracing" as a dependency I can create a reproducer later.... |
@pwlan any change you have a reproducer? It would really help in narrowing down what is going on here. |
Of course Just run the tests. Any other questions, just let me know. |
Great, thanks! |
Use proper type for serializing Kotlin response
Fixes: quarkusio#28096 (cherry picked from commit 26f53a7)
Describe the bug
Hi,
thanks for the fix of #23678
But it looks like this has introduced a new issue.
When using Lists, the following error ocurrs.
The issue can be easily reproduced:
or
In the case of a list, the Kotlin ListSerializer needs to be used. The same applies to Sets.
Quarkus Version
Quarkus 2.12.2
Expected behavior
It should produce beautiful json.
Originally posted by @pwlan in #23678 (comment)
The text was updated successfully, but these errors were encountered: