-
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
Custom ContextResolver can not be used anymore for rest client since 3.13 #46411
Labels
Milestone
Comments
/cc @cescoffier (rest-client), @geoand (rest-client) |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Feb 21, 2025
The context resolver resolution could well be happening as part of JAX-RS Client call and not a high level REST Client call Fixes: quarkusio#46411
Good point! #46413 fixes the issue |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Feb 21, 2025
The context resolver resolution could well be happening as part of JAX-RS Client call and not a high level REST Client call Fixes: quarkusio#46411
cescoffier
added a commit
that referenced
this issue
Feb 24, 2025
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Feb 24, 2025
The context resolver resolution could well be happening as part of JAX-RS Client call and not a high level REST Client call Fixes: quarkusio#46411 (cherry picked from commit ee4a8f7)
jmartisk
pushed a commit
to jmartisk/quarkus
that referenced
this issue
Feb 27, 2025
The context resolver resolution could well be happening as part of JAX-RS Client call and not a high level REST Client call Fixes: quarkusio#46411 (cherry picked from commit ee4a8f7)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Between 3.12.3 and 3.13.0, an regression was introduced.
During my transition period from resteasy to resteasy-reactive, I needed to reliably set the used ObjectMapper for a rest client. No matter if the app run with classic or reactive. I came up with following:
The code is obviously a few years old at this point, and I believe quarkus now automatically registers the pre configured object mapper, for classic and reactive.
When I try to use the client from above, I get the exception below in 3.13.0. With 3.12.3, worked fine.
For me, the workaround was to remove my custom context resolver.
Might still be interesting to investigate this, since this pattern is allowed according to spec afaik.
Expected behavior
Rest client should work
Actual behavior
How to Reproduce?
man-rest-client.zip
Unzip
mvn quarkus:dev
curl localhost:8080/hello-invoker
error
change version in pom to 3.12.3
curl localhost:8080/hello-invoker
works
Output of
uname -a
orver
Microsoft Windows [Version 10.0.26100.3194]
Output of
java -version
openjdk 23.0.2 2025-01-21 OpenJDK Runtime Environment Temurin-23.0.2+7 (build 23.0.2+7) OpenJDK 64-Bit Server VM Temurin-23.0.2+7 (build 23.0.2+7, mixed mode, sharing)
Quarkus version or git rev
3.12.3, 3.13.0
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) Maven home: C:\eclipse\tools\java\maven Java version: 23.0.2, vendor: Eclipse Adoptium, runtime: C:\eclipse\tools\java\23 Default locale: de_DE, platform encoding: UTF-8 OS name: "windows 11", version: "10.0", arch: "amd64", family: "windows"
Additional information
No response
The text was updated successfully, but these errors were encountered: