 <p>In Spring 4 it is possible to autowire by parameter types declaration. There is no need for qualifier if you use interface with Generics:</p> <pre><code>@Autowired private IProcessContextFactory&lt;OrderEntity, OrderEntity&gt; processContextFactory; </code></pre> <p>This is the least possible coupling as you could add mock implementation with the same parameters and autowire mock instead. With the qualifier, there is direct dependency on specific bean with a given name. As another thing to consider, you would have to cast to <code>OrderEntity</code>explicitly and that sort of kills the point of parameterized interface.</p> <p>However, you can also do it with qualifier and concrete type, but that is reudndant:</p> <pre><code>@Autowired @Qualifier("PricingProcessContextFactory") private IProcessContextFactory&lt;OrderEntity, OrderEntity&gt; processContextFactory; </code></pre> <p>As to why your example doesn't work, although it looks like it should, i will give you my best guess, but i cannot back this up with some source.</p> <p>Imagine if you had two implementations of Generic interface, and each of these implementations are <code>@Service</code> with some name and data types.</p> <p>When you autowire implementation of Generic interface parameterized with Object, Spring has two possible candidates for implementation. The only way for Spring to know which bean to inject here would be by the qualifier name.</p> <p>Since there is already mechanism to resolve Generic interface implementations by type, existence of qualifier would have to be prioritized and used instead of type declarations. But since the autowire by data type declaration offers much lower coupling, and this is how it is documented that should be used on Spring site, i guess autowiring of implementation with object parameter types is not supported as it is inferior option.</p> <p><a href="http://spring.io/blog/2013/12/03/spring-framework-4-0-and-java-generics" rel="nofollow">Spring Autowiring Generics</a></p>