2 beans with same name but in different packages; how to autowire them?

spring inversion-of-control autowired
Marco picture Marco · Jun 13, 2012 · Viewed 29.2k times · Source

I have an application that has 2 beans with the same name, but which are in different packages. My Spring application fails because it cannot decide on which bean to take. Is there any solution for this? The beans do not currently implement specific interfaces.

See below an edited example of the exception:

Caused by:
org.springframework.context.annotation.ConflictingBeanDefinitionException:
Annotation-specified bean name 'dataTransferHandler' for bean class
[aaaaa.ws.handler.DataTransferHandler] conflicts with existing,
non-compatible bean definition of same name and class
[bbbbb.ws.handler.DataTransferHandler]

Answer

Biju Kunjummen picture Biju Kunjummen · Jun 13, 2012

You will have to give your beans different names - if multiple beans are defined with the same name, then the one defined later will override the one defined earlier - so in your case only one bean will exist with the name of dataTransferHandler.

You can give these two beans different names, so that both can exist and you can inject in the correct one either using: @AutoWired @Qualifier("dataTransferHandler") OR @Resource(name="dataTransferHandler")

Related questions

Defining the same Spring bean twice with same name

Is having two definition for a bean (with same name and class) valid in Spring IOC ? I am having two bean definition files included in web.xml. See the sample below. applicationContext-beans1.xml <bean name="myWao" class="com.beans.…

Read More
How to avoid using ApplicationContext.getBean() when implementing Spring IOC

I'm just getting started with Spring IOC concept. I often see most of the examples found in the internet use the code to get the object. ApplicationContext appContext = new ClassPathXmlApplicationContext("applicationContext.xml"); Hello hello = (Hello) appContext.getBean("hello"); As a …

Read More
FactoryBeans and the annotation-based configuration in Spring 3.0

Spring provides the FactoryBean interface to allow non-trivial initialisation of beans. The framework provides many implementations of factory beans and -- when using Spring's XML config -- factory beans are easy to use. However, in Spring 3.0, I can't find a …

Read More