Everything is brilliant until I encounter place where I actually do need to catch exception. When I place
jdbcTemplate.query(something...)
You should catch the JdbcTemplate exception
i.e.
try
{
// Your Code
}
catch (InvalidResultSetAccessException e)
{
throw new RuntimeException(e);
}
catch (DataAccessException e)
{
throw new RuntimeException(e);
}
InvalidResultSetAccessException is a DataAccessException so that no need to catch it in your case. And DataAccessException is already a RuntimeException so that no need to throw a Runtime exception. But you should throw a specific exception of your application such as :
try
{
// Your Code
}
catch (DataAccessException e)
{
throw new MyApplicationException("A problem occurred while retrieving my data", e);
}
That's because SQLException
, a checked exception, is not thrown by the any of the JdbcTemplate.query(...)
methods (javadoc link). Spring translates this to one of the DataAccessException, which is more generic family of runtime exceptions, in order to abstract away any specific underlying database implementation.