-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Response.fromResponse bug in reactive version of resteasy libs #41887
Milestone
Comments
/cc @FroMage (resteasy-reactive), @stuartwdouglas (resteasy-reactive) |
Thanks for the reproducer. This is a duplicate of #25496 |
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Aug 27, 2024
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Aug 27, 2024
gastaldi
added a commit
to gastaldi/quarkus
that referenced
this issue
Aug 27, 2024
danielsoro
pushed a commit
to danielsoro/quarkus
that referenced
this issue
Sep 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We switched from resteasy legacy to recomended reactive alternative quarkus-rest, quarkus-rest-jacskon.
After switch we noticed that Response.fromResponse method does not work anymore.
Code in controllers like
Response.fromResponse(rcClient.doCall()).build()
was working for legacy libs and its not correctly working in new libs.
It returns correct status, but payload somehoiw cannot be accessed.
I created reproducer
https://github.com/bkalas/q3-responsebug-reproducer
there are 2 projects
'reproducer-reactive-not-working'
'reproducer-resteasy-legacy-working'
See in both MainRestController and test for it, in resteasy-legacy test will pass, same test wont pass for rective
Expected behavior
Bahviour should be same for both libraries
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
17
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: