Pre-process GraphQL schema resources at build time #29291
Labels
for: external-project
For an external project and not something we can fix
status: superseded
An issue that has been superseded by another
theme: aot
An issue related to Ahead-of-time processing
type: enhancement
A general enhancement
Comments
bclozel
added
the
status: blocked
|
Blocked until a Spring for GraphQL version with Jakarta API is available. |
|
hi - i'm sorry I'm missing something. What does Jakarta EE have to do with Spring Graphql and its ability to resolve |
|
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. |
|
We've started brainstorming how we could do this for entities and that issue looks like yet another case for that need. See #30523. |
mbhave
added
theme: aot
|
Closing in favor of spring-projects/spring-graphql#495 |
bclozel
added
for: external-project
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As seen in spring-projects/spring-graphql#218 (comment), 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 spring-projects/spring-graphql#230 (comment)).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.
The text was updated successfully, but these errors were encountered: