So, that's it for Google Guice. To sum up our chapter, we began with basic dependency injection. After that, we learned how basic Dependency Injection works in Guice, with examples.
Then, we investigated the phases of Guice, and the role of the API in each phase. We got the idea that, unlike Spring, in Guice there is no requirement to maintain isolated XML files, as all the setup-related data is nicely typified by means of the module component.
In the middle of the chapter, we explored the major annotations and distinct types of binding available in Guice, and at the end, we learned the different types of injections.
In the next chapter, we will become competent in the different scopes offered by Spring and the Google Guice framework ...
