Up until Spring 4 generics played no major role when it came to resolving injected bean dependencies. Suppose there are multiple beans of the same type implementing a generic interface. In a pre-Spring 4 world, any attempt to resolve such a bean by type would inevitably lead to a NonUniqueBeanDefinition Read more…
In this post, I will look into the distinction between a component and a bean. Even though both of them refer to Spring managed beans, each serves a different purpose. @Component and its specializations (@Controller, @Service and @Repository) allow for auto-detection using classpath scanning. @Bean on the other hand can Read more…
Last time, when I talked about lazily loaded beans I forgot to mention one interesting feature of Spring 4 – lazily loaded injection points. This post introduces the combination of @Lazy and @Autowire as a counterpart to the standard approach (JSR-330) using @Inject and Provider. As of Spring 4.0 @Lazy Read more…
Lazy initialization allows for a greater flexibility and performance by delaying bean instantiation to the very last moment. A fairly straightforward feature represented by a simple annotation @Lazy. Yet, as usual, there are a few pitfalls to watch out for. Let’s start with some trivia. Adding @Lazy on the class Read more…
Last time I talked about @Primary and @Autowire as a useful means of dependency injection. Today I will brief you on how @Autowire compares to its more standard counterpart @Resource and demonstrate @Qualifier as a handy complement to @Autowire. Both @Autowire and @Resource serve the same purpose, i.e. finding the Read more…
With a recent upgrade of my favorite framework I was thinking a short recap wouldn’t harm. This very first post, from a series of articles on Spring’s features I find interesting, deals with intricacies of injecting the right bean out of a range of suitable candidates. If you are keen to Read more…