-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
json format issue with quarkus 2.5.0.Final at patch request #21768
Comments
Can you please attach a sample project the exhibits the problem you mention? |
@geoand I updated it with github repository link for sample |
I see that your reproducer depends on another service that is not included. So I used what you specified in the issue: @Path("/testPath")
public class MyResource {
@PATCH
@Path("/{id}")
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
public Response myPatch(@PathParam("id") String id){
return Response.ok(id).build();
}
} and it worked as expected |
I checked that #21818 and I think it's the same issue |
Very interesting. Let's close this then since the underlying issue has already been fixed. Once 2.5.1 is out, please give it a try and comment if the issue has not been fixed |
Describe the bug
I was using quarkus 2.4.1.Final and implemented a patch request with quarkus-resteasy-jackson
now, I need to update to 2.5.0.Final but when I try updating it, the format of response is not right and I get an error parsing JSON data.
Expected behavior
the expected was to have the same json response as before
Actual behavior
the response code is 200 as before but with miss match json format - error to parse json
How to Reproduce?
find sample project for the problem: https://github.com/RehamAboelyazied7/mongo-with-quarkus
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
The text was updated successfully, but these errors were encountered: