[
https://issues.jboss.org/browse/CDI-274?page=com.atlassian.jira.plugin.sy...
]
Pete Muir updated CDI-274:
--------------------------
Fix Version/s: 1.1 (Proposed)
Definitely +1 from me. We should probably do a full review of all methods on BeanManager
like this.
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
Fix For: 1.1 (Proposed)
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