Using Spring JDBC


JDBC was a significant achievement when it first appeared on the scene nearly a decade ago. It provided a clean, clear abstraction for interfacing with any database, staying true to the platform-independence credo of Java. But in practice, JDBC can be quite a difficult beast to tame. Working with a database may seem simple at first, but a lot is happening under the abstraction hood, meaning there’s plenty of room for things to go awry. Interacting with a database implicitly means interfacing with a driver, making a connection over a network, and finally initiating SQL calls in which data is passed back and forth between your application and the external database. JDBC does a great job of abstracting this large stack of processes and protocols, but with so much complexity and margin for error, you can easily see how your code might grow commensurately, in order to address all the potential problems and error conditions that might arise.


Configuration File Domain Object Person Reference Template Pattern Public Person 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Copyright information

© Paul Tepper Fisher and Solomon Duskis 2009

Personalised recommendations