-
Notifications
You must be signed in to change notification settings - Fork 672
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
Add SPI mechanism for ahead-of-time repository fragment registration #3090
Comments
This was referenced Aug 26, 2024
Closed
mipo256
pushed a commit
to mipo256/spring-data-commons
that referenced
this issue
Sep 21, 2024
Repositories that detect fragment implementations implementing RepositoryMetadataAccess enable metadata exposure regardless of the exposeMetadata flag. See: spring-projects#3090 Original Pull Request: spring-projects#3145
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, we scan for fragments on the class path and either register fragments to the
BeanFactory
or use existing beans. It would be neat to have mechanism to register fragments for a particular repository upfront so that fragments can be provided as already-discovered collection of implementation classes for repository inclusion.The text was updated successfully, but these errors were encountered: