-
as seen on Programmers
- Search for 'Programmers'
On the Wikipedia page on dependency injection, the disadvantages section tells us this:
Dependency injection increases coupling by requiring the user of a subsystem to provide for the needs of that subsystem.
with a link to an article against dependency injection.
Dependency injection makes…
>>> More
-
as seen on Gooder Code
- Search for 'Gooder Code'
It’s no secret I am a fan of dependency injection. So I was happy to hear that Dick Wall of the Java Posse recently released a dependency injection framework for scala. Called SubCut, or Scala Uniquely Bound Classes Under Traits, the project is a ‘mix of service locator and dependency…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I find that my constructors are starting to look like this:
public MyClass(Container con, SomeClass1 obj1, SomeClass2, obj2.... )
with ever increasing parameter list. Since "Container" is my dependency injection container, why can't I just do this:
public MyClass(Container con)
for every class…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
Can anyone point me towards some good documentation / code examples on how best to manage the configuration of a DI container in a scenario where you need different configuations sets?
We have a layered, distributed application that has multiple entry points (ie; a website, winforms app, office plugin…
>>> More
-
as seen on Stack Overflow
- Search for 'Stack Overflow'
I'm trying to introduce DI as a pattern here at work and one of our lead developers would like to know: What - if any - are the downsides to using the Dependency Injection pattern?
Note I'm looking here for an - if possible - exhaustive list, not a subjective discussion on the topic.
>>> More
