Skip to main content

Spring Test Case Class

For a real-life integration test it is generally more appropriate to load the context in the JUnit setUp() method and closed in the tearDown(), so that each test method does not have to repeat the step of invoking ApplicationContext get the the beans.

One concern is that while this will avoid code duplication, the context will still be created once for each test method, as calls to setup()/teardown() surround each test method invocation. JUnit does this to ensure fresh base test benefit, the base class is capable of  triggering the direct injection of dependencies into the test case class, via setter injection(autowired by type), or field injection matching by name ,as below,
public class WeatherServiceTest extends
    AbstractDependencyInjectionSpringContextTests {
    
  private WeatherService weatherService;
    
  public void setWeatherService(WeatherService weatherService) {
    this.weatherService = weatherService;
  }
    
  protected String[] getConfigLocations() {
    return new String[]{"ch03/sample3/applicationContext.xml"};
  }
    
  public void testWeatherService() throws Exception {
    Double high = weatherService.getHistoricalHigh(
        new GregorianCalendar(2004, 0, 1).getTime());
    // ... do more validation of returned value here...
  }
}

Comments

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…