[
https://issues.jboss.org/browse/WELD-1061?page=com.atlassian.jira.plugin....
]
Stuart Douglas resolved WELD-1061.
----------------------------------
Resolution: Rejected
This behaviour is ok, according to the spec bean resolution is not required to work in
AfterBeanDiscovery (also it is possible to add more beans in this stage)
Inconsistent results from BeanManager.getBeans(Type, Annotation .. )
after AfterBeanDiscovery event
----------------------------------------------------------------------------------------------------
Key: WELD-1061
URL:
https://issues.jboss.org/browse/WELD-1061
Project: Weld
Issue Type: Bug
Components: Weld SPI
Affects Versions: 1.1.5.Final
Environment: fedora core 14 linux 32b, windows vista 32b
Reporter: Marko Milenković
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
scenario project:
https://github.com/milenkovicm/examples/tree/master/weld
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira