posted 13 years ago
In general that approach is backwards: you *do* want to wrap up underlying exceptions with less-specific ones.
In this case, if you're using Spring's SQL support, you're going to get Spring exceptions--if you don't want that, my first instinct would be to not use Spring's SQL support. It's not clear to me why you'd want to do anything different.