useRepositoryConfiguration(...) fails for repositories with multiple store modules on the class path if at least one does not support reactive repositories.
This is, because RepositoryConfigurationExtensionSupport checks whether the configuration should be used first and then it checks whether the store module is actually responsible for the repository interface.
We should delay the useRepositoryConfiguration(...) check until the store responsibility is clarified
Issue Links:
DATACMNS-1174 Improve error reporting for not supported repository interfaces
Mark Paluch opened DATACMNS-1389 and commented
useRepositoryConfiguration(...)
fails for repositories with multiple store modules on the class path if at least one does not support reactive repositories.This is, because
RepositoryConfigurationExtensionSupport
checks whether the configuration should be used first and then it checks whether the store module is actually responsible for the repository interface.We should delay the
useRepositoryConfiguration(...)
check until the store responsibility is clarifiedIssue Links:
Backported to: 2.0.10 (Kay SR10)
The text was updated successfully, but these errors were encountered: