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.
I am building a application framework with Spring and Hibernate. I want to write a Service Layer ( Business Logic Layer ) which will effectively and efficiently call the Hibernate DAO bean methods with help of Spring Framework.
Consider a case where one application functionality requires to interact with 3 - 4 tables. Each table will be Entity having a Hibernate DAO class.How will my service layer call 3 - 4 DAO classes? Is there a better design which will suffice this scenario. Basically I want to write a Service Layer which will be capable getting data talking to all DAO classes efficiently.
If your service use case requires multiple DAOs to succeed, then just inject those DAOs into your Service class. That is exactly the design that should be followed. There are indeed dependencies, and now they are still loosely coupled with Spring injection.