As seen in https://github.com/spring-projects/spring-graphql/pull/218#issuecomment-997296408, using our Spring GraphQL auto-configuration with the experimental Spring Native project is causing issues.
The Spring Boot auto-configuration for Spring GraphQL is scanning classpath locations for files using the PathMatchingResourcePatternResolver. This approach is not compatible for now with GraalVM (see https://github.com/spring-projects/spring-graphql/issues/230#issuecomment-1007386842).
When a Spring Framework abstraction allows it, we should pre-process this at build time using the upcoming AOT engine and programmatically configure those resources on the GraphQL source builder directly.
Comment From: bclozel
Blocked until a Spring for GraphQL version with Jakarta API is available.
Comment From: joshlong
hi - i'm sorry I'm missing something. What does Jakarta EE have to do with Spring Graphql and its ability to resolve Resources?
Comment From: wilkinsona
It's a more general blockage at the moment. Spring for GraphQL uses Jakarta EE APIS (such as the Servlet API, for example) and there is not yet a version of Spring for GraphQL that uses the EE 9 versions of those APIs.
Comment From: snicoll
We've started brainstorming how we could do this for entities and that issue looks like yet another case for that need. See #30523.
Comment From: bclozel
Closing in favor of spring-projects/spring-graphql#495