Changing Accept Header in PreMatching filter isn't considered by MessageBodyWriter #41097
Comments
|
Thanks for reporting. #41111 takes care of it and should be backported to both 3,11 and 3.8 (the LTS release) |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Jun 11, 2024
geoand
added a commit
that referenced
this issue
Jun 11, 2024
Take MediaType set in pre-match filter into when returning Response
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Jun 11, 2024
Fixes: quarkusio#41097 (cherry picked from commit 57f38f1)
holly-cummins
pushed a commit
to holly-cummins/quarkus
that referenced
this issue
Jul 31, 2024
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Aug 14, 2024
Fixes: quarkusio#41097 (cherry picked from commit 57f38f1)
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
#40019 fixed the routing to correct MessageBodyWriters in case that response is POJO. For JAX WS Response remains the old behavior.
Expected behavior
Accept Header set in the pre-matching request filter shall decide which MessageBodyWriter will be selected, even if returned value is JAX WS Response.
Actual behavior
Setting the Accept Header inside the pre-matching request filter doesn't affect which MessageBodyWriter is being selected in case that return type is JAX WS Response.
How to Reproduce?
checkout https://github.com/myroch/quarkus-prematching-servermessagebodywriter-bug
run ExampleResourceTest
Output of
uname -aorverNo response
Output of
java -versionjava 17.0.9 2023-10-17 LTS
Quarkus version or git rev
3.11.1
Build tool (ie. output of
mvnw --versionorgradlew --version)Apache Maven 3.9.6
Additional information
No response
The text was updated successfully, but these errors were encountered: