Prior to Spring 3.0, most APIs did not use generics because Java 1.5 was not required. The result was RowMapper, which did not support generics and ParameterizedRowMapper, which supported generics, extending RowMapper and adding a generic parameter. Starting with Spring 3.0, most of the APIs have been updated to support generics. If you really look at the current (3.0 or higher) definition of ParameterizedRowMapper, it just simply extends RowMapper and doesn't add anything to the definition to provide backward compatibility. Therefore, you can pretty much use RowMapper, parameterized or not, and you don't need to use the ParameterizedRowMapper parameter.
source share