in the JDBC Tutorial that comes with the STS, I can see where the dataSource is injected into the transactionManager.

And I can see how the Customer, CustomerService and SpringJDBCIntro classes are tied together.

I can even see that the CustomerService is where the magic is happening. What I am not seeing is how the CustomerService interface and the dataSource/transactionManager are getting glued together. I assume that that is where the magic juju is happening that actually hooks the Service methods up to the persistence engine.

What I am not seeing is "What is telling the Spring Framework what concrete class to use for the CustomerService?"