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):
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):