Spring Programmatic Transaction Management

This means that you have manage the transaction with the help of programming. That gives you extreme flexibility, but it is difficult to maintain.

Programmatic transaction management is usually a good idea only if you have a small number of transactional operations. For example, if you have a web application that require transactions only for certain update operations, you may not want to set up transactional proxies using Spring or any other technology. In this case, using the TransactionTemplate may be a good approach. Being able to set the transaction name explicitly is also something that can only be done using the programmatic approach to transaction management.
Popular Spring Tutorials

1. Spring Tutorial
2. Spring MVC Web Tutorial
3. Spring Boot Tutorial
4. Spring JDBC Tutorial
5. Spring AOP Tutorial
6. Spring Security Tutorial

On the other hand, if your application has numerous transactional operations, declarative transaction management is usually worthwhile. It keeps transaction management out of business logic, and is not difficult to configure. When using the Spring Framework, rather than EJB CMT, the configuration cost of declarative transaction management is greatly reduced.

Let us see how above mentioned steps work but before we begin, it is important to have at least one database tables on which we can perform various CRUD operations with the help of transactions. Let us take Employee table, which can be created in MySQL DAVDB database with the following DDL:

CREATE TABLE Employee(
   EMPID   INT NOT NULL AUTO_INCREMENT,
   NAME VARCHAR(26) NOT NULL,
   AGE  INT NOT NULL,
   SALARY BIGINT NOT NULL,
   PRIMARY KEY (EMPID)
);

1. Create a project with a name SpringTMDemo and create a package com.dineshonjava.sdnext under the src folder in the created project.

2. Add required Spring libraries using Add User Libs option as explained in the Spring Hello World Example chapter.
3. Add other required libraries mysql-connector-java.jar
4.Create DAO interface EmpDAO and list down all the required methods. Though it is not required and you can directly write EmployeeDaoImpl class, but as a good practice, let's do it.
EmpDAO.java

package com.dineshonjava.sdnext.dao;

import java.util.List;

import com.dineshonjava.sdnext.domain.Employee;

/**
 * @author Dinesh Rajput
 *
 */
public interface EmpDao {
 
 /** 
  * This is the method to be used to create
  * a record in the Employee table.
  */
 void create(String name, Integer age, Long salary);
 /** 
  * This is the method to be used to list down
  * a record from the Employee table corresponding
  * to a passed Employee id.
  */
 Employee getEmployee(Integer empid);
 /** 
  * This is the method to be used to list down
  * all the records from the Employee table.
  */
 List listEmployees();
 /** 
  * This is the method to be used to delete
  * a record from the Employee table corresponding
  * to a passed Employee id.
  */
 void delete(Integer empid);
 /** 
  * This is the method to be used to update
  * a record into the Employee table.
  */
 void update(Integer empid, Integer age);
}

EmployeeDaoImpl.java

package com.dineshonjava.sdnext.dao.impl;

import java.util.List;

import org.springframework.dao.DataAccessException;
import org.springframework.jdbc.core.support.JdbcDaoSupport;
import org.springframework.stereotype.Component;
import org.springframework.transaction.PlatformTransactionManager;
import org.springframework.transaction.TransactionDefinition;
import org.springframework.transaction.TransactionStatus;
import org.springframework.transaction.support.DefaultTransactionDefinition;

import com.dineshonjava.sdnext.dao.EmpDao;
import com.dineshonjava.sdnext.domain.Employee;
import com.dineshonjava.sdnext.jdbc.utils.EmployeeMapper;

/**
 * @author Dinesh Rajput
 *
 */
@Component
public class EmployeeDaoImpl extends JdbcDaoSupport implements EmpDao {
// @Autowired
// private JdbcTemplate jdbcTemplateObject;
// 
// /**
//  * @param jdbcTemplateObject the jdbcTemplateObject to set
//  */
// public void setJdbcTemplateObject(JdbcTemplate jdbcTemplateObject) {
//  this.jdbcTemplateObject = jdbcTemplateObject;
// }

private PlatformTransactionManager transactionManage;

 public void setTransactionManager(
      PlatformTransactionManager transactionManager) {
      this.transactionManager = transactionManager;
   }

@Override
public void create(String name, Integer age, Long salary) {
  TransactionDefinition def = new DefaultTransactionDefinition();
  TransactionStatus status = transactionManager.getTransaction(def);
try {
 String SQL = "INSERT INTO Employee (name, age, salary) VALUES (?, ?, ?)";
 getJdbcTemplate().update(SQL, new Object[]{name, age, salary} );
 transactionManager.commit(status);
System.out.println("Created Record Name = " + name + " Age = " + age+ " Salary = " + salary);
 // to simulate the exception.
 throw new RuntimeException("simulate Error condition") ;
  } catch (DataAccessException e) {
       System.out.println("Error in creating record, rolling back");
       transactionManager.rollback(status);       
       throw e;
    }
}

 @Override
 public Employee getEmployee(Integer empid) {
  String SQL = "SELECT * FROM Employee WHERE empid = ?";
  Employee employee = (Employee) getJdbcTemplate().queryForObject(SQL, new Object[]{empid}, new EmployeeMapper());
     return employee;
 }

 @Override
 public List listEmployees() {
  String SQL = "SELECT * FROM Employee";
  List employees = (List) getJdbcTemplate().query(SQL, new EmployeeMapper());
     return null;
 }

 @Override
 public void delete(Integer empid) {
  String SQL = "DELETE FROM Employee WHERE empid = ?";
  getJdbcTemplate().update(SQL, new Object[]{empid});
  System.out.println("Deleted Record with EMPID = " + empid );
 }

 @Override
 public void update(Integer empid, Integer age) {
   String SQL = "UPDATE Employee SET age = ? WHERE empid = ?";
   getJdbcTemplate().update(SQL, new Object[]{age, empid});
   System.out.println("Updated Record with EMPID = " + empid );
 }
}