Skip to content
This repository has been archived by the owner on Dec 19, 2023. It is now read-only.

Request scoped beans aren't accessible in mutation and query resolvers #959

Open
bsara opened this issue Jul 18, 2023 · 0 comments
Open

Comments

@bsara
Copy link

bsara commented Jul 18, 2023

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:

  1. Create a request scoped bean
  2. 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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant