[
https://issues.jboss.org/browse/CDI-274?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-274:
-----------------------------------
either that or move the point of the check from currently AfterDeploymentValidation to
AfterBeanDiscovery.
This feature got introduced to prevent Extensions from behaving randomly depending on the
scan order. If we agree that AfterBeanDiscovery is a save enough point, then I'm also
fine with it.
BeanManager#getBeans() shall throw an Exception if called before
AfterDeploymentValidation
------------------------------------------------------------------------------------------
Key: CDI-274
URL:
https://issues.jboss.org/browse/CDI-274
Project: CDI Specification Issues
Issue Type: Bug
Components: Beans
Affects Versions: 1.1.EDR
Reporter: Mark Struberg
Assignee: Pete Muir
Fix For: 1.1.PFD
We recently had the erroneous case in DeltaSpike that an Extension did call
BeanManager#getBeans() in an @Observes ProcessBean method.
Doing so leads to random behaviour as the result of getBeans() depends on the order in
which the other beans got processed already. E.g. getBeans(Object.class) will return an
empty list for the first bean getting processed, and will return all beans -1 for the last
bean. That just makes no sense and will create unreproducible bugs.
PROPOSAL:
We shall add spec language to BeanManager#getBeans() that any invocation before the
AfterDeploymentValidation phase will result in a deployment error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira