Skip to main content

Spring - Database Transaction (Part 2)

Transaction Interceptor is an appropriate solution when you want as much control over the transaction processing as possible. Because this solution uses a regular AOP proxyFactoryBean, it allows us to use additional interceptors for other purposes.
The interceptor is specified as a bean named TransactionInterceptor. This interceptor bean has a proprty called transactionAttributeSource that specified as MethodMapTransactionAttributeSource continning the fully qualified method names of the target class and the transaction nattributes that should be in effect for this transaction.The method names can contains an * as a wildcard either at the end or the beginning of the name. Afte the method name you can specify propagation behavior, isolation level, timeout value , and a readonly flag in any order.

 In addition to the mentioned transaction attributes, you can also specify additional rollback and no-rollback attributes based on an exception class. These attributes indicate the desired behavior in terms of transaction commit/rollback when the specified exception is thrown during the transaction processing.

<!-- The DBCP DataSource -->
  <bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource"
    <property name="driverClassName">
    <property name="url"><value>${jdbc.url}</value></property>
    <property name="username"><value>${jdbc.username}</value></property>
    <property name="password"><value>${jdbc.password}</value></property>
  <!-- The DAO class -->
  <bean id="dao"
    <property name="dataSource">
      <ref local="dataSource"/>
  <!-- The transactionmanager to use for regular non JTA datasource -->
  <bean id="transactionManager"
    <property name="dataSource">
      <ref local="dataSource"/>
  <!-- TransactionInterceptor -->
  <bean id="transactionInterceptor"
    <property name="transactionManager">
      <ref bean="transactionManager"/>
    <property name="transactionAttributeSource">
  <!-- Transactional proxy for the primary business object -->
  <bean id="boxOffice"
    <property name="target">
      <ref local="boxOfficeTarget"/>
    <property name="proxyInterfaces">
    <property name="interceptorNames">
  <!-- Business Object -->
  <bean id="boxOfficeTarget"
    <property name="boxOfficeDao">
      <ref local="dao"/>


Popular posts from this blog

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold highlighted in example below) which resolve the problems.   example:
<band height="20" splitType="Stretch"> <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/> …

JasperReports - Configuration Reference

Spring - Operations with jdbcTemplate

This class manages all the database communication and exception handling using a java.sql.Connection that is obtained from the provided DataSource. JdbcTemplate is a stateless and threadsafe class and you can safely instantiate a single instance to be used for each DAO.

Use of Callback Methods
JdbcTemplate is based on a template style of programming common to many other parts of Spring. Some method calls are handled entirely by the JdbcTemplate, while others require the calling class to provide callback methods that contain the implementation for parts of the JDBC workflow. This is another form of Inversion of Control. Your application code hands over the responsibility of managing the database access to the template class. The template class in turn calls back to your application code when it needs some detail processing filled in. These callback methods are allowed to throw a java.sql.SQLException, since the framework will be able to catch this exception and use its built-in excepti…