This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Originally posted by Amir Rafique: I want to use Spring DAO Framework in my application but I donot want to use the dependency injection of the Spring. Can any one please give me any hint.
I've never done this, but I suspect that it wouldn't be that hard. Rather than let Spring instantiate and wire up the data source, template, and DAO classes, you do it programatically in your own code. Under the covers, Spring's DI is only calling setter methods to do the wiring...no reason you couldn't call those same setters and do the wiring yourself.
But I am curious why you will forsake Spring DI. Are you using a different DI mechanism? Or do you just have something against DI in general?