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

resteasy-reactive: When using own Content-Types for @Produces entity is always serialized with toString (resteasy-reactive 1.11.0.Beta1) #14023

Closed
holledauer opened this issue Dec 22, 2020 · 2 comments · Fixed by #14027
Assignees
Labels
area/rest kind/bug Something isn't working
Milestone

Comments

@holledauer
Copy link

Describe the bug
Using @Produces with non-standard content type does not work with resteasy-reactive. It will always serialize with toString.

Expected behavior
It should serialize with the correct serializer depending on the content type (e.g. jackson when Content-Type ends with +json)

Actual behavior
It serializes with toString()

To Reproduce

Steps to reproduce the behavior:

  1. Checkout https://github.com/quarkusio/quarkus-quickstarts/tree/development/hibernate-reactive-quickstart
  2. Change version to 1.11.0.Beta1
  3. Add @Produces("application/vnd.quarkus.fruit-v1+json") to POST method
  4. Call curl -H "Content-Type: application/vnd.quarkus.fruit-v1+json" http://localhost:8080/fruits -d'{"name": "apple"}' -v
@holledauer holledauer added the kind/bug Something isn't working label Dec 22, 2020
@ghost ghost added the area/rest label Dec 22, 2020
@ghost
Copy link

ghost commented Dec 22, 2020

/cc @FroMage, @geoand, @stuartwdouglas

@geoand geoand self-assigned this Dec 22, 2020
@geoand
Copy link
Contributor

geoand commented Dec 22, 2020

I have a fix for this but it breaks some of the TCK tests which means I'll need to dig into it more

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rest kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants