JdbcClient should be avaiable when Spring JDBC and Jdbc Drivers in the classpath

[hantsy]

When I want to use JdbcClient in Spring Boot 3.5.0-M1, I have to add starter-data-jdbc, even though I have added spring-jdbc and the jdbc drivers.

[wilkinsona]

Thanks for trying the milestone.

I have to add starter-data-jdbc, even though I have added spring-jdbc and the jdbc drivers.

That shouldn't be the case. Perhaps you could look at the condition evaluation report (launch your app with --debug) to identify why JdbcClientAutoConfiguration wasn't used.

If that doesn't help and you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

[hantsy]

The example project is here, https://github.com/hantsy/spring7-sandbox/tree/master/boot-vibur-dbcp

Try to comment the starter-data-jdbc in pom.xml and run the test DemoApplicationTests, it will throw an exception that indicate it can not find JdbcClient bean.

[wilkinsona]

Without spring-boot-starter-data-jdbc there's no JDBC connection pool on the classpath for which Spring Boot has auto-configuration support so there's no JDBC infrastructure. You can see this in the condition evaluation report, some relevant sections of which are:

   JdbcClientAutoConfiguration:
      Did not match:
         - @ConditionalOnSingleCandidate (types: org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate; SearchStrategy: all) did not find any beans (OnBeanCondition)

   JdbcTemplateAutoConfiguration:
      Did not match:
         - @ConditionalOnSingleCandidate (types: javax.sql.DataSource; SearchStrategy: all) did not find any beans (OnBeanCondition)
      Matched:
         - @ConditionalOnClass found required classes 'javax.sql.DataSource', 'org.springframework.jdbc.core.JdbcTemplate' (OnClassCondition)

   DataSourceAutoConfiguration.EmbeddedDatabaseConfiguration:
      Did not match:
         - EmbeddedDataSource found supported pooled data source (DataSourceAutoConfiguration.EmbeddedDatabaseCondition)

   DataSourceConfiguration.Dbcp2:
      Did not match:
         - @ConditionalOnClass did not find required class 'org.apache.commons.dbcp2.BasicDataSource' (OnClassCondition)

   DataSourceConfiguration.Generic:
      Did not match:
         - @ConditionalOnProperty (spring.datasource.type) did not find property 'spring.datasource.type' (OnPropertyCondition)

   DataSourceConfiguration.Hikari:
      Did not match:
         - @ConditionalOnClass did not find required class 'com.zaxxer.hikari.HikariDataSource' (OnClassCondition)

   DataSourceConfiguration.OracleUcp:
      Did not match:
         - @ConditionalOnClass did not find required classes 'oracle.ucp.jdbc.PoolDataSourceImpl', 'oracle.jdbc.OracleConnection' (OnClassCondition)

   DataSourceConfiguration.Tomcat:
      Did not match:
         - @ConditionalOnClass did not find required class 'org.apache.tomcat.jdbc.pool.DataSource' (OnClassCondition)

If you use spring-boot-starter-jdbc, HikariCP will be on the classpath and things will work as expected.

Alternatively, as already described in #43986, if you want to use Vibur than you should use DataSourceBuilder to define a DataSource bean.