Hi. In my application, I have domain objects like : Book, Author, Publisher (I'm using Hibernate).... I created interfaces like BookDAO, AuthorDAO and then implement them using HibernateDaoSupport. But while I'm coding my DAO's, a question came into my mind : Is it good to many DAOs (like my case) or to create a master DAO called for example : BookStoreDAO ? What is the right approach here ? Thanks folks
I recomend many daos if you are planning to reuse your code. You can just take the things you need and leave everything else out of your new project. It is also easier to work when you are doing maintenance because you know exactly in which dao you need to do the corrections. Well just my opinion.
She will remember your heart when men are fairy tales in books written by rabbits.<br /> As long as there is duct tape... there is also hope.