Next I refactor the DI configuration towards an easy-to-use API.
2011-03-24
Let's Code Dimdwarf #44: Making the Dependencies Explicit
The main principle of dependency injection is to make all dependencies of a module explicit. By refactoring the hard coded DI configuration so that the dependencies between modules become more explicit and the duplication more obvious, the design desired by the code begins to emerge.
2011-03-17
Let's Code Dimdwarf #43: It's Alive!
Now that a hard coded manual dependency injection configuration is working, it will be possible to begin refactoring it and remove all duplication, until a reusable framework or DSL emerges.
2011-03-13
Let's Code Dimdwarf #42: Without DI Frameworks
I had an idea to see how the program would fare without a Dependency Injection (DI) framework such as Guice. It should be possible to use just manual DI. It might even be much simpler that way. To find out, I will do a spike.
2011-03-09
Let's Code Dimdwarf #41: Class Loader Trouble
When the class loader reads something from a JAR file, it will lock that JAR file so that it cannot be deleted, and there is no way to explicitly dispose of a ClassLoader. Only in Java 7 will there be a solution (see the ApplicationLoadingSpec after some changes I did off-screen).
2011-03-06
2011-03-01
Let's Code Dimdwarf #40: Better Asserts
Creating your own assert methods is oftentimes useful, to make the test code and the assertion messages read better. In this episode I will also write a test for class loading from JAR files.
Subscribe to:
Posts (Atom)