我正在使用SpringJUnit4ClassRunner来运行我的集成测试。我不得不在Spring Boot REST Web服务中使用两个数据源,因为我想使用不同的数据库用户进行Liquibase和Application查询。当我运行测试时,第二个数据源没有被创建。
以下是我的测试代码
@RunWith(SpringJUnit4ClassRunner.class)
@SpringApplicationConfiguration(classes = Application.class)
@WebAppConfiguration
@IntegrationTest
public class DomainServiceImplTest {
@Test
public void testCreateDomain() throws Exception {
}
}
以下是我的数据源实例化
@Configuration
@EnableTransactionManagement
public class DatabaseConfiguration {
private final Logger log = LoggerFactory.getLogger(DatabaseConfiguration.class);
@Inject
private Environment env;
@Autowired(required = false)
private MetricRegistry metricRegistry;
@Bean(destroyMethod = "close")
@Primary
public DataSource dataSource(DataSourceProperties dataSourceProperties, NileRegistrarProperties nileRegistrarProperties) {
log.debug("Configuring Datasource");
if (dataSourceProperties.getUrl() == null) {
log.error("Your database connection pool configuration is incorrect! The application" +
" cannot start. Please check your Spring profile, current profiles are: {}",
Arrays.toString(env.getActiveProfiles()));
throw new ApplicationContextException("Database connection pool is not configured correctly");
}
HikariConfig config = new HikariConfig();
config.setDriverClassName(dataSourceProperties.getDriverClassName());
config.setJdbcUrl(dataSourceProperties.getUrl());
if (dataSourceProperties.getUsername() != null) {
config.addDataSourceProperty("user", dataSourceProperties.getUsername());
} else {
config.addDataSourceProperty("user", ""); // HikariCP doesn't allow null user
}
if (dataSourceProperties.getPassword() != null) {
config.addDataSourceProperty("password", dataSourceProperties.getPassword());
} else {
config.addDataSourceProperty("password", ""); // HikariCP doesn't allow null password
}
//MySQL optimizations, see https://github.com/brettwooldridge/HikariCP/wiki/MySQL-Configuration
if ("com.mysql.jdbc.jdbc2.optional.MysqlDataSource".equals(dataSourceProperties.getDriverClassName())) {
config.addDataSourceProperty("cachePrepStmts", nileRegistrarProperties.getDatasource().isCachePrepStmts());
config.addDataSourceProperty("prepStmtCacheSize", nileRegistrarProperties.getDatasource().getPrepStmtCacheSize());
config.addDataSourceProperty("prepStmtCacheSqlLimit", nileRegistrarProperties.getDatasource().getPrepStmtCacheSqlLimit());
}
if (metricRegistry != null) {
config.setMetricRegistry(metricRegistry);
}
return new HikariDataSource(config);
}
@Bean(destroyMethod = "close")
public DataSource liquibaseDataSource(DataSourceProperties dataSourceProperties, LiquibaseProperties liquibaseProperties) {
log.debug("Configuring Liquibase Datasource");
if (dataSourceProperties.getUrl() == null) {
log.error("Your database connection pool configuration is incorrect! The application" +
" cannot start. Please check your Spring profile, current profiles are: {}",
Arrays.toString(env.getActiveProfiles()));
throw new ApplicationContextException("Database connection pool is not configured correctly");
}
HikariConfig config = new HikariConfig();
config.setDriverClassName(dataSourceProperties.getDriverClassName());
config.setJdbcUrl(dataSourceProperties.getUrl());
// Close all connections after liquibase operation is complete.
config.setMinimumIdle(0);
if (dataSourceProperties.getUsername() != null) {
config.addDataSourceProperty("user", liquibaseProperties.getUser());
} else {
config.addDataSourceProperty("user", ""); // HikariCP doesn't allow null user
}
if (dataSourceProperties.getPassword() != null) {
config.addDataSourceProperty("password", liquibaseProperties.getPassword());
} else {
config.addDataSourceProperty("password", ""); // HikariCP doesn't allow null password
}
return new HikariDataSource(config);
}
@Bean
public SpringLiquibase liquibase(@Qualifier("liquibaseDataSource") DataSource dataSource,
LiquibaseProperties liquibaseProperties) {
// Use liquibase.integration.spring.SpringLiquibase if you don't want Liquibase to start asynchronously
SpringLiquibase liquibase = new AsyncSpringLiquibase();
liquibase.setDataSource(dataSource);
liquibase.setChangeLog("classpath:config/liquibase/master.xml");
liquibase.setContexts(liquibaseProperties.getContexts());
liquibase.setDefaultSchema(liquibaseProperties.getDefaultSchema());
liquibase.setDropFirst(liquibaseProperties.isDropFirst());
liquibase.setShouldRun(liquibaseProperties.isEnabled());
log.debug("Configuring Liquibase");
return liquibase;
}
}
以下是错误消息。
Error creating bean with name 'dataSourceInitializer': Invocation of init method failed;
当我使用单一数据源时,一切正常。
答案 0 :(得分:1)
我正在开发一个类似的项目,我有两个数据源。这是我做的,
datasource.primary.url=jdbc:mysql://localhost:3306/databaseName
datasource.primary.username=username
datasource.primary.password=password
对于第二个数据源,
datasource.secondary.url=jdbc:mysql://localhost:3306/databaseName
datasource.secondary.username=username
datasource.secondary.password=password
在config类中,只做,
@Bean
@Primary
@ConfigurationProperties(prefix = "datasource.primary")
public DataSource primaryDataSource() {
return DataSourceBuilder.create().build();
}
@Bean(name = "secondaryDatasource")
@ConfigurationProperties(prefix = "datasource.secondary")
public DataSource secondaryDataSource() {
return DataSourceBuilder.create().build();
}
无论我需要数据源,我只需将其自动装配:
public void setJdbcTemplate(@Qualifier("secondaryDatasource") DataSource dataSource) {
this.jdbcTemplate = new NamedParameterJdbcTemplate(dataSource);
}
注意:如果在自动装配时未使用@Primary
,则会注入带注释的@Qualifier
数据源。
测试更加简单。如果要在内存数据库中进行测试(最常用的技术),只需提供另一组属性,使用内存数据库的url,可供测试类使用