Timeline for Dependency injection: should I use a framework?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2017 at 3:02 | comment | added | Thorbjørn Ravn Andersen | IntelliJ understands CDI (Java EE standard DI) | |
| Nov 12, 2016 at 21:18 | comment | added | Basilevs | It would be great to IDE part, with the runtime binding of injections framework as opposed to design time type binding of manual injections. Compiler prevents forgotten injections when they are manual. | |
| May 17, 2016 at 0:09 | comment | added | RubberDuck | That's unfortunate @WinstonEwert. Thanks for filling in the context for me. | |
| May 16, 2016 at 23:38 | comment | added | Winston Ewert | @RubberDuck, in my case, I worked for a large company with a large number of java projects all standardized on the same dependency injection framework. At that point it becomes tempting for some teams to export a library that expects to be put together by the DI framework, rather then providing a sensible external interface. | |
| May 16, 2016 at 22:41 | comment | added | RubberDuck | This is a very good answer, but I can't imagine using an IoC container for a class library. That feels like poor design to me. I would expect a library to have me explicitly give it whatever dependencies it requires. | |
| May 16, 2016 at 4:25 | history | answered | Winston Ewert | CC BY-SA 3.0 |