We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using non-string parameters with reactive REST client, you get a class-cast exception.
Non-string parameters should be converted to string using ParamConverter or eventually toString.
All parameters are casted to String, hence class cast exception.
Run SimpleTest from this repo/branch
uname -a
ver
No response
java -version
2.6.2.Final
mvnw --version
gradlew --version
This works for non-reactive REST client.
The text was updated successfully, but these errors were encountered:
/cc @michalszynkiewicz
Sorry, something went wrong.
Take ParamConverterProvider into account for form params in REST Clie…
fd2f594
…nt Reactive Fixes: quarkusio#23034
1715389
Merge pull request #23041 from geoand/#23034
6c8c259
Take ParamConverterProvider into account for form params in REST Client Reactive
b4ade63
…nt Reactive Fixes: quarkusio#23034 (cherry picked from commit 1715389)
geoand
Successfully merging a pull request may close this issue.
Describe the bug
When using non-string parameters with reactive REST client, you get a class-cast exception.
Expected behavior
Non-string parameters should be converted to string using ParamConverter or eventually toString.
Actual behavior
All parameters are casted to String, hence class cast exception.
How to Reproduce?
Run SimpleTest from this repo/branch
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
2.6.2.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
This works for non-reactive REST client.
The text was updated successfully, but these errors were encountered: