Tuesday, December 15, 2020

Spring JdbcTemplate With ResultSetExtractor Example

In the post Select Query Using JDBCTemplate in Spring Framework we have already seen an example of extracting data from ResultSet using RowMapper. A RowMapper is usually a simpler choice for ResultSet processing, mapping one result object per row but there is another option in Spring framework known as ResultSetExtractor which gives one result object for the entire ResultSet. In this post we’ll see an example of Spring JdbcTemplate with ResultSetExtractor.

Since ResultSetExtractor is a callback interface used by JdbcTemplate's query methods so you can use an instance of ResultSetExtractor with JdbcTemplate’s query method.

query method signature with ResultSetExtractor

public <T> T query(java.lang.String sql, ResultSetExtractor<T> rse) throws DataAccessException

After the execution of the query, ResultSet can be read with a ResultSetExtractor.

ResultSetExtractor interface in Spring

ResultSetExtractor interface is a functional interface used by JdbcTemplate’s query method. It has a single abstract method extractData().

T extractData(java.sql.ResultSet rs) throws java.sql.SQLException, DataAccessException

Implementing class must implement this method to process the entire ResultSet.

Spring JdbcTemplate with ResultSetExtractor example

Technologies used

Spring 5.0.4
Apache DBCP2
MYSQL 5.1.39
Java 8
Apache Maven 3.3.3

Maven dependencies

If you are using Apache Maven then you can provide dependencies in your pom.xml.

Refer Creating a Maven project in Eclipse to see how to set up Maven project.

With all the dependencies your pom.xml should look something like this-

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">




    <!-- Spring JDBC Support -->
   <!-- MySQL Driver -->
    <!--  Apache DBCP connection pool -->

Alternatively you can download the jars and add them to the class path.

Database table

For this example I have created a table called employee with the columns id, name and age in the MYSQL DB. Column id is configured as auto increment checked so no need to pass id from your query as DB will provide value for it.

CREATE TABLE `employee` (
  `name` varchar(35) DEFAULT NULL,
  `age` int(11) DEFAULT NULL,
  PRIMARY KEY (`id`)

Setting up bean dependencies

In the bean for JdbcTemplate you will need to set the DataSource bean as dependency. In the DataSource bean you will need to provide DB properties. It is better if you read DB configuration parameters from a properties file.

Property file db.properties which is under the config folder has all the properties.



Description for the properties used here is as-

driver class name is the JDBC driver for the DB used. Since MYSQL is used here so the jdbc driver for the same (com.mysql.jdbc.Driver) is provided.

Url – You need to provide url to access your DB server. I have created a schema called netjs and DB is running on the same system so url is jdbc:mysql://localhost:3306/netjs.

Username and password for the DB.

IntialSize is the initial size of the connection pool. It is given as 5 so initially 5 connections will be created and stored in the pool.

XML Configuration

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
    <context:property-placeholder location="classpath:config/db.properties" />                  

    <context:component-scan base-package="org.netjs.daoimpl" />
    <bean id="dataSource" class="org.apache.commons.dbcp2.BasicDataSource">
      <property name="driverClassName" value = "${db.driverClassName}" />
      <property name="url" value = "${db.url}" />
      <property name="username" value = "${db.username}" />
      <property name="password" value = "${db.password}" />
      <property name="initialSize" value = "${pool.initialSize}" />
    <bean id="jdbcTemplate" class="org.springframework.jdbc.core.JdbcTemplate">  
      <property name="dataSource" ref="dataSource"></property>  

Java Classes

Since Spring always promotes to use interfaces and there is also a JEE design pattern for database layer called DAO which also says the same thing - Separate low level data access code from the business layers.

So we have a EmployeeDAO interface with find methods and its implementing class EmployeeDAOImpl. There is also a model class Employee with all the getters/setters.

Employee.java class

public class Employee {
 private int empId;
 private String empName;
 private int age;
 public int getEmpId() {
  return empId;
 public void setEmpId(int empId) {
  this.empId = empId;
 public String getEmpName() {
  return empName;
 public void setEmpName(String empName) {
  this.empName = empName;
 public int getAge() {
  return age;
 public void setAge(int age) {
  this.age = age;
EmployeeDAO interface
import org.netjs.model.Employee;
public interface EmployeeDAO {
    public List<Employee> findAllEmployees();

EmployeeDAOImpl class

public class EmployeeDAOImpl implements EmployeeDAO {
  private JdbcTemplate jdbcTemplate; 

  final String SELECT_ALL_QUERY = "SELECT id, name, age from EMPLOYEE";
  public void setJdbcTemplate(JdbcTemplate jdbcTemplate) {  
    this.jdbcTemplate = jdbcTemplate;  
  public List<Employee> findAllEmployees() {
    return this.jdbcTemplate.query(SELECT_ALL_QUERY, 
    new ResultSetExtractor<List<Employee>>() {
      public List<Employee> extractData(ResultSet rs)
            throws SQLException, DataAccessException {
        List<Employee> list = new ArrayList<Employee>();  
          Employee emp = new Employee();
        return list;

Notice how you are not writing any code for getting or closing connection, exception handling. All that fixed part is managed by the JdbcTemplate class. Its the JdbcTemplate which is getting the connection using the DataSource provided to it, creating and executing the statement and closing the connection.

If there is any SQLException thrown that is also caught by JdbcTemplate and translated to one of the DataAccessException and rethrown.

ResultSetExtractor interface is implemented as an anonymous inner class and you can see the implementation of extractData method where the returned ResultSet is processed.

Test class

You can use the following code in order to test the code -
public class App {
  public static void main(String[] args) {    
    ClassPathXmlApplicationContext context = new ClassPathXmlApplicationContext("appcontext.xml");
    EmployeeDAO dao = (EmployeeDAO)context.getBean("employeeDAOImpl");  
    List<Employee> empList = dao.findAllEmployees();
    for(Employee emp : empList){
      System.out.println("Name - "+ emp.getEmpName() + " Age - " 
        + emp.getAge());

ResultSetExtractor implemented as a Lambda expression

Since ResultSetExtractor is a functional interface so Java 8 onwards it can also be implemented as lambda expression.

public List<Employee> findAllEmployees() {
  return this.jdbcTemplate.query(SELECT_ALL_QUERY, (ResultSet rs) -> {
    List<Employee> list = new ArrayList<Employee>();  
      Employee emp = new Employee();
    return list;

That's all for this topic Spring JdbcTemplate With ResultSetExtractor Example. If you have any doubt or any suggestions to make please drop a comment. Thanks!

>>>Return to Spring Tutorial Page

Related Topics

  1. Spring NamedParameterJdbcTemplate Insert, Update And Delete Example
  2. Spring NamedParameterJdbcTemplate Select Query Example
  3. registerShutdownHook() Method in Spring Framework
  4. Excluding Bean From Autowiring in Spring
  5. @Resource Annotation in Spring Autowiring

You may also like-

  1. @Conditional Annotation in Spring
  2. Spring util-namespace Example For Wiring Collection
  3. Circular Dependency in Spring Framework
  4. AutoBoxing And UnBoxing in Java
  5. Volatile Keyword in Java With Examples
  6. AtomicInteger in Java With Examples
  7. StringBuilder Class in Java With Examples
  8. Array in Java With Examples