News for hackers. Stuff that matters.

A comment on Spring vs. Java EE. Parent comment

Re:Spring vs. Java EE by spiralpolitik on Sunday April 09, 2017 @05:11PM (#14074390)
With Constructor based injection its easier to see layering and coupling issues as once your constructor gets more that 3-4 parameters then it starts becoming blindingly obvious that the class has too many dependencies and needs to be refactored. This helps keep the bad out of the architecture.

The main reason to favor constructor based injection is that it stops objects becoming 'live' in an inconsistent state. I've seen actual production issues with setter based injection that can only be explained by the object being available for use before all the setters have been called.

[ Parent | on HN ]
Re:Spring vs. Java EE by ivan_gammel on Monday April 10, 2017 @01:52AM (#14076373)
Your arguments are valid on why constructor injection should be preferred. However, what are you talking about is the human-made decision: "Stop adding more parameters to constructor". The tool does not force you to build high-quality architecture, it is your choice based on your experience and skills. Other people who are not yet aware about the consequences may still make wrong design decisions and they'll be ok with lots of parameters.
[ Parent | on HN ]