-
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
Resteasy Reactive detects multiple writers, but only one response type is present #14720
Comments
/cc @FroMage, @geoand, @stuartwdouglas |
Does the |
@geoand yes, indeed it does in this example. |
Understood. I'll check it out soon |
…resolution of builders By making certain writers extend AllWriteableMessageBodyWriter we can be certain that even in the presense of multiple writers, RESTEasy Reactive can optimize itself to use only the first one Fixes: quarkusio#14720
…resolution of builders By making certain writers extend AllWriteableMessageBodyWriter we can be certain that even in the presense of multiple writers, RESTEasy Reactive can optimize itself to use only the first one Fixes: quarkusio#14720
…resolution of builders By making certain writers extend AllWriteableMessageBodyWriter we can be certain that even in the presense of multiple writers, RESTEasy Reactive can optimize itself to use only the first one Fixes: quarkusio#14720
Ensure that ServerStringMessageBodyHandler doesn't affect build time resolution of builders
…resolution of builders By making certain writers extend AllWriteableMessageBodyWriter we can be certain that even in the presense of multiple writers, RESTEasy Reactive can optimize itself to use only the first one Fixes: quarkusio#14720 (cherry picked from commit 2321d0c)
I believe this regressed in 1.13.1.Final (same in 1.13.2.Final). In 1.13.0.Final it was ok. |
I'll take a look tomorrow |
I created a small reproducer explaining what I did because I think this is for jackson only, with jsonb works good |
Thanks |
#16578 should fix the issue |
Ensure that Jackson writer doesn't negatively affect endpoint score
thanks @geoand. Can you clarify also if it is supposed for the score showing 0% when returning a Response object, because it says it only finds the writer in runtime? I was expecting that |
Yes, I can confirm that this is the intended behavior. The problem is that because |
@geoand I wonder if we should introduce a typed version of Response in RESTEasy Reactive with a proper type argument. It wouldn't be as flexible as you would define the type but I think it could work in a lot of cases. |
Yes we have thought about it. If I am not mistaken, @FroMage had a branch with that |
Yup. FroMage@bc744d9 But it's really a POC. I think it would make for a good feature, though. And since it's the second time other people than me have mentioned it, it's probably time to open an issue for it: #16718 |
Fixes quarkusio#14720 (comment) (cherry picked from commit bc4fbf6)
Fixes quarkusio#14720 (comment) (cherry picked from commit bc4fbf6)
Describe the bug
I have a GET method annotated with
@Produces(MediaType.APPLICATION_JSON)
.In the Score Console it says however that I have 2 writers for this method:
This negativly affects the score of this method. See screenshot.
Expected behavior
RR should not detect a simple Produces(MediaType.APPLICATION_JSON) as multiple writers.
To Reproduce
Steps to reproduce the behavior:
Screenshots
Environment (please complete the following information):
Linux martin 5.8.0-41-generic Add proper logging #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
openjdk 11.0.7 2020-04-14 LTS
OpenJDK Runtime Environment Zulu11.39+15-CA (build 11.0.7+10-LTS)
OpenJDK 64-Bit Server VM Zulu11.39+15-CA (build 11.0.7+10-LTS, mixed mode)
1.11.1.Final
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /home/martin/.sdkman/candidates/maven/current
Java version: 11.0.7, vendor: Azul Systems, Inc., runtime: /home/martin/.sdkman/candidates/java/11.0.7-zulu
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.8.0-41-generic", arch: "amd64", family: "unix"
The text was updated successfully, but these errors were encountered: