/explore
|
You are here 
|
msfjarvis.dev | ||
| | | | |
adambennett.dev
|
|
| | | | | Android Bennett's blog :: android, kotlin, thoughts, opinions, occasional rants | |
| | | | |
ryanharter.com
|
|
| | | | | I recently gave a presentation about how Dagger works under the hood, and I was once again struck by the elegance of the javax.inject.Provider interface. The interface is so simple it almost seems useless, but it's also incredibly flexible, and forms the basis of much of the code generated by Dagger. Like many dependency injection frameworks for JVM languages, Dagger uses and builds on the standard set of annotations for injectable classes defined in JSR-330 and provided in the javax. | |
| | | | |
sookocheff.com
|
|
| | | | | Inversion of Control (IoC), also known as Dependency Injection (DI), allows an object to define their dependencies as constructor arguments (strictly speaking, you can set these dependencies as properties, but the examples I will use today are constructor-based). This is the inverse of the object itself controlling the instantiation or location of its dependencies, hence the name Inversion of Control. Let's look at an example from Stackoverflow using a text editor with a spell checking component: | |
| | | | |
fusectore.dev
|
|
| | | This is the first part in a series of articles on dependency injection for the play framework using guice. As soon as Ive written the next part, it will be linked here. Please note that while the examples are written in Scala, the principles apply for Java likewise. Furthermore, please be aware that Guice is not the only framework to do dependency injection with. It is probably the most prominent one in the play ecosystem though. Guice does so called runtime dependency injection. This means dependencies ... | ||
