You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Repositories that detect fragment implementations implementing RepositoryMetadataAccess enable metadata exposure regardless of the exposeMetadata flag.
See: #3090
Original Pull Request: #3145
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
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: