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
{{ message }}
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.
Describe the bug
I'm seeing that request scoped beans aren't accessible/initiated in mutation and query resolvers regardless of running in async mode or not. Specifically those beans that are scoped via the @Scope(value = WebApplicationContext.SCOPE_REQUEST, proxyMode = ScopedProxyMode.TARGET_CLASS) or @RequestScope annotations.
To Reproduce
Steps to reproduce the behavior:
Create a request scoped bean
Attempt to access the bean from step one on a mutation resolver via auto wiring into the mutation resolver bean class
Expected behavior
I can access the request scoped bean in the mutation resolver just as I would in a restful controller class.
Desktop (please complete the following information):
OS: MacOS
Version 13
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
I'm seeing that request scoped beans aren't accessible/initiated in mutation and query resolvers regardless of running in async mode or not. Specifically those beans that are scoped via the
@Scope(value = WebApplicationContext.SCOPE_REQUEST, proxyMode = ScopedProxyMode.TARGET_CLASS)
or@RequestScope
annotations.To Reproduce
Steps to reproduce the behavior:
Expected behavior
I can access the request scoped bean in the mutation resolver just as I would in a restful controller class.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: