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
DATACMNS-1596 - Modules not exposing identifying annotations do not claim repository interfaces anymore.
Previously, a module not exposing any entity identifying annotations would have claimed a repository definition and potentially overrode the bean definition of another store that was the proper claim in the first place. We have now changed this to abstain from a claim of the interface.
We' also tweaked the log output in the following cases:
1. If the module neither returns an identifying type nor entity identifying annotations, we now log a warning that a module does not support a multi-module setup and answer all assignment requests with false.
2. The info level warning indicating an interface has been dropped now reports which annotations or interface base types to use.
Original pull request: #411.
Related tickets: spring-projects/spring-boot#18721
privatestaticfinalStringCLASS_LOADING_ERROR = "%s - Could not load type %s using class loader %s.";
56
-
privatestaticfinalStringMULTI_STORE_DROPPED = "Spring Data {} - Could not safely identify store assignment for repository candidate {}.";
57
+
privatestaticfinalStringMULTI_STORE_DROPPED = "Spring Data %s - Could not safely identify store assignment for repository candidate %s. If you want this repository to be a %s repository,";
58
+
59
+
privatebooleannoMultiStoreSupport = false;
57
60
58
61
/*
59
62
* (non-Javadoc)
@@ -338,7 +341,22 @@ protected <T extends RepositoryConfigurationSource> RepositoryConfiguration<T> g
Copy file name to clipboardExpand all lines: src/test/java/org/springframework/data/repository/config/RepositoryConfigurationExtensionSupportUnitTests.java
0 commit comments