Loading...

XML

Word

Printable

Steps to Reproduce:
Hide

scenario to reproduce the incostencies:

create a simple CDI project and a class, lets name it SimpleClass

create a simple CDI extension and inject BeanManager in it

create observer method for AfterBeanDiscovery and AfterDeploymentValidation lifecycle events

beanManager.getBeans(SimpleClass.class) returns 0 results if called in AfterBeanDiscovery observer method

beanManager.getBeans(SimpleClass.class) returns 1 results if called in AfterDeploymentValidation observer method
Show
scenario to reproduce the incostencies: create a simple CDI project and a class, lets name it SimpleClass create a simple CDI extension and inject BeanManager in it create observer method for AfterBeanDiscovery and AfterDeploymentValidation lifecycle events beanManager.getBeans(SimpleClass.class) returns 0 results if called in AfterBeanDiscovery observer method beanManager.getBeans(SimpleClass.class) returns 1 results if called in AfterDeploymentValidation observer method
Forum Reference:
https://community.jboss.org/thread/180218

scenario to reproduce the incostencies:

create a simple CDI project and a class, lets name it SimpleClass
create a simple CDI extension and inject BeanManager in it
create observer method for AfterBeanDiscovery and AfterDeploymentValidation lifecycle events
beanManager.getBeans(SimpleClass.class) returns 0 results if called in AfterBeanDiscovery observer method
beanManager.getBeans(SimpleClass.class) returns 1 results if called in AfterDeploymentValidation observer method
beanManager.getBeans(Object.class) returns correct results in both cases

Looks like that BeanManager doesn't have correct bean types after AfterBeanDiscovery phase. I can't find any details about this behaviour in JSR299.

weld and weld-core version is 1.1.5.Final