CDI, several managed beans of the same type

[Sergei Zhylinski]

Hello,

I'm familiarizing myself with CDI. I've started with the standalone applications. I'm using Jboss Weld for this. I can't really create several beans of the same type. Spring framework in contrast allows to register several beans in XML configuration file of the same type but with different bean names/ids:

<?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans"   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"   xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> <bean name="dummyPerformer" class="com.test.spring_fw.beans.Performer" > </bean> <bean name="performer1" class="com.test.spring_fw.beans.Performer" > <property name="name" value="John Doe" /> <property name="country" value="USA" /> </bean> </beans>

After that I'm able to retrieve a bean from the context by its name:

		ApplicationContext ac = new FileSystemXmlApplicationContext("/tmp_f/beans.xml"); // BeanDefinitionStoreException в случае, если файл не найден (см. соответсвующий файл с логом)
		Performer performer = ac.getBean("dummyPerformer", Performer.class);
		System.out.println(performer.getName() + " " + performer.getCountry()); // null null
		performer = ac.getBean("performer1", Performer.class);
		System.out.println(performer.getName() + " " + performer.getCountry()); // John Doe USA

But all the tutorials found in the net devoted to CDI and Weld have similar code example:

        Weld weld = new Weld();
        WeldContainer container = weld.initialize();
        Performer performer = container.instance().select(Performer.class).get();
        System.out.println(performer.getName() + " " + performer.getCountry()); // null null
        weld.shutdown();

Is it possible to create several performers and put them into CDI META-INF/beans.xml file?

[Sergei Zhylinski]

Now I think that no. The beans.xml configuration file is not used to declare beans. It mainly indicates that the archive is a candidate for bean scan. The CDI implementations use only bean scan similar to component scan in Spring. It dosn't assume explicitely registering any of the beans in the config.