Another best practice question. How should JDBC access be handled when using Spring? The Spring tutorials I've seen on the subject to date all have separate data access objects for each database object that users might wish to query or update. Traditionally when doing JDBC I've tended to write one Data Access Layer class that handles all JDBC interactions. Is this an outdated approach?
Don't know if it's best practice or not but Spring 4.x (anyway) has that JDBCTemplate thing you may use to set up those CRUD operations similar to a DAO implementation. I believe the DB connection is injected when you use the template.
By the way, I personally haven't use the JDBCTemplate recently.