-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
@RequestScope with Filter and reactive routes #13073
Comments
Probably a cleaning related to this: https://quarkus.io/guides/cdi-reference#request-context-lifecycle |
^--------- This one is interesting. It seems the filter ends before the route method is executed. UPDATE: Hm, this happens because the |
UPDATE: I've sent a draft PR that should fix this problem: #13458 |
If there is a route filter and the request can have body (POST, PUT, etc.) then the route method is invoked asynchronously (once all data are read). However, the request context is activated by the filter and so we need to make sure the same context is then used in the route method. - resolves quarkusio#13073
When I set a data in TestFilter to RequestScopedService, I cannot get data from this bean after because a new instance of RequestScopedService is created (if the request is a type POST / PUT / DELETE)
Actual behavior
To Reproduce
Run project in additional context
Environment (please complete the following information):
uname -a
orver
:java -version
: Java version: 11.0.8, vendor: GraalVM Community, runtime: graalvm-ce-java11-20.2.0Additional context
(Add any other context about the problem here.)
bug-request-scope.tar.gz
The text was updated successfully, but these errors were encountered: