Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to create a DAO layer for my application. After some googling I found that many peoples uses Generic DAO approach (Don’t repeat the DAO!).
But I did not like this approach.
What if I need slightly different interfaces between DAO for different DAO implementations? (i.e. methods in generic interface not exactly same which I want to create in my DAO implementations)
What if my entity’s primary key consists of more than one attribute?
If you need a slightly different DAO for a particular entity, you can always extend a generic one(
MySpecificDAO <....> extends GenericDAO<....>). Primary key can be composite itself, but it’s impossible to have 2 primary keys .