You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A ServerResponseFilter is always executed even when it is constrained by a @NameBinding annotation and the annotation is not used.
In this example, the annotation alters the response context status code. However, the annotation is not used in the resource, yet the status code changes.
Expected behavior
The response filter should not be applied since the @namebinding annotation is not used.
Describe the bug
A ServerResponseFilter is always executed even when it is constrained by a
@NameBinding
annotation and the annotation is not used.In this example, the annotation alters the response context status code. However, the annotation is not used in the resource, yet the status code changes.
Expected behavior
The response filter should not be applied since the @namebinding annotation is not used.
Actual behavior
The filter is applied.
How to Reproduce?
Run the test in the following repo:
https://github.com/romilpunetha/quarkus-test-filter
Output of
uname -a
orver
Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000 arm64
Output of
java -version
openjdk version "17.0.2" 2022-01-18
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.9.2.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Maven home: /opt/homebrew/Cellar/maven/3.8.5/libexec
Additional information
No response
The text was updated successfully, but these errors were encountered: