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.
Say I use a simple frontend for information passed on by a DAO that uses JDBC (without ORM). In other words, the class would have no attributes to speak of. Would this considered as a valid approach? What issues could it potentially cause and how could a class be designed to avoid them?
It sounds like you are referring to the data transfer object pattern. So long as the pattern fits your needs, it is a valid approach. I’m not aware of any pitfalls as such.