The Spring JDBC wrapper offers at least the following: - a further abstraction away from iBatis (which is useful if you wish to change the underlying persistence framework in the future)
- common data access exceptions (i.e. the iBatis exceptions are mapped to spring exceptions. Again, useful if you want to reduce dependency on iBatis). There are other benefits, especially when the rest of what Spring offers is taken into account, e.g. transparent transaction handling. I recommend having a look at chapter 11 of the Spring reference documentation. regards richard
