Was searching for how to do Dependency Injection through constructor in Spring when i found this article. Covers some good basics on Springs DI and some JDBC fundamentals as well.
I’ve switched to constructor DI on one of my services. I was getting tired of all the setters cluttering my code. 😉
As a newbie developer I’ve been thinking a lot lately about where to put responsibilities and behaviour in systems I develop. It seems quite common for most developers to default to the DTO pattern and just dumb objects. Fine grained value objects might not be real DTOs, but it is in the same tradition of not having behaviour in the objects. I see some proponents mean it’s bad OOD, and it probably is. I’m not just sure what will work best for me yet. 😉
I was reading this post on Jon Tirsens blog on the usage of DTOs when I came across Domain Driven Design by Eric Evans. I’ll have to pick it up some day. I just have to finish up reading for JCP and J2EE without EJB first. 😉
We all know it happens. You start a project with a solid set of requirements, but they just keep changing. That’s why you plan for change. Fowler tackles this by ScopeLimbering.