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 have made an app and I experimented in two scenarios. Make a bean extend a Hibernate db object, or make the bean clear distinct from db object.
In the first case, I had a quick way to access data. A quick way to make interfaces in the end of different beans extending the same db table. In the second case, I had to load the external inside the beans and go on.
Which way is the “by-the-book” way? Both seemed pretty nice, but I liked the first. Or shouldn’t I ?
This is a much more general question of “composition vs inheritance”, and is independent of Spring and Hibernate.
See this other answer for a full description/argument.
Briefly, while it’s sometimes tempting to extend another class for convenience, you almost always end up regretting it later. Go the extra mile, compose your objects rather than extend them, and you’ll win over the longer term.