-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check for and eliminate duplicate schema resource registrations #230
Comments
I've isolated the I don't think the issue is about replacing resources - as this happens only in JVM mode since both scanned schema resources and resources manually set with a customizer are present, leading to duplicates. In native mode, this doesn't happen since the first set of resources are not discovered. The code snippet listed in #218 (comment) looks fine to me - and this should actually be quite close to what we should do in the future: an AOT processor should discover those resources at build time, register them as resources against the native image, and then generate code that does such manual registration. In summary, I don't think we need to change the current behavior. |
I've created spring-projects/spring-boot#29291 to follow up on this. |
After a team discussion, I'm reopening this issue to also improve the situation for Boot 2.7. @joshlong pointed out in #218 (comment) that using |
A
GraphQlSourceBuilderCustomizer
might need to replace the default schema resources, e.g. #218 (comment).The text was updated successfully, but these errors were encountered: