Comments on: Constructor Injection vs. Setter Injection

By: Dependency Injection – The What And The How « Binary Thoughts : IEnumerable<T>

Mon, 05 Jul 2010 06:18:18 +0000

[...] very distinct styles of injection are Constructor Injection and Setter Injection. Constructor injection takes dependencies using the constructor like the code above – it [...]

By: marcus kielly

marcus kielly — Thu, 25 Mar 2010 22:23:22 +0000

I tend to pass arguments in arrays if there are more than 3 arguments, and unpack the array in the constructor. Then again, I’m a filthy PHP coder…

By: Craig Harris

Craig Harris — Sat, 02 Jan 2010 02:40:22 +0000

@Artur,

The builder pattern would appear to solve many of the problems you are seeing.

By: misko

misko — Fri, 01 Jan 2010 17:59:58 +0000

@Artur,

Yes too many arguments in your constructor is a code smell. It means that your object has too many responsibilities and needs to be broken up.

By: Artur Ejsmont

Artur Ejsmont — Wed, 30 Dec 2009 16:59:14 +0000

Hi there

Im not sure yet how much i like constructor injection but i know i dont like setter injection. You should not be able to create non functioning object. Init methods and magic calls needed to make instance work are code smell as well i would say.

The problem i would agree with is that in constructor injection you have no clear names for parameters (in some frameworks only order tells you what to insert) and if you have too many of them code begins to look bit nasty.

By: Berlin Brown

Berlin Brown — Fri, 18 Dec 2009 15:31:18 +0000

This is probably a stupid question, but how do you deal with constructor injection and too many arguments. Should we create everything and the kitchen sink objects and then pass that as our constructor?

By: firefight

firefight — Wed, 15 Jul 2009 19:26:47 +0000

Nice article. I think the problem with your view of setter injection is that you have “reasonable defaults”. With Spring you do not have any reasonable defaults, they are null by default, so your app will fail quickly and obviously, rather then appear to work, if the setters are not called. It sounds like you were doing all of the setting in code once per object, rather then specifying them once per class, like you do in Spring.

Personally I’m not fond of setter injection, either. I like my objects immutable if possible, and it just seems like a lot of extra code and configuration, that is rarely ever used to extend the application anyway.

By: Constructor Injection vs Setter Injection « shaun smith

Constructor Injection vs Setter Injection « shaun smith — Fri, 01 May 2009 17:56:41 +0000

[...] Constructor Injection vs Setter Injection Constructor vs Setter Injection – Constructor is Better Setter injection versus constructor injection and the use of required [...]

By: Using (These) Anonymous Inner Classes is Probably Too Clever for Your Own Good at JAW Speak

Wed, 11 Mar 2009 04:33:14 +0000

[...] It uses setters. Setters allow your object to be constructed in an inconsistent state. There are some situations setters are fine (i.e. form backing objects) but often your code is more clear without setters. In this particular case the setters aren’t egregious, but I still consider them a smell and much more verbose way that constructor injection. Read more about the problem with setter injection here [...]

By: Integrazione JSF e Spring « A Place In The Queue

Integrazione JSF e Spring « A Place In The Queue — Mon, 02 Mar 2009 19:41:19 +0000

[...] tramite costruttore, che personalmente preferisco rispetto all’ approccio via setter. Questo articolo di Miško Hevery spiega i motivi della mia personalissima scelta « [...]