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
I'm pleased to hear that you've found a workaround. An alternative that you might like to consider is to mark one of your DataSource beans as @Primary.
Also, you may be interested to know that the general situation will improve in 1.4.0.M2 when #2784 is implemented. It will mean that the initialiser backs off when there are multiple DataSource beans to choose from rather than failing as it currently does.
DataSourceInitializer init method fails, because it works only if there is just one DataSource bean in the context>
if (this.applicationContext.getBeanNamesForType(DataSource.class, false, false).length > 0) { this.dataSource = this.applicationContext.getBean(DataSource.class); }
Either change condition in if clause to "== 0" or handle org.springframework.beans.factory.NoUniqueBeanDefinitionException prope
The text was updated successfully, but these errors were encountered: