[cdi-dev] [JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called
[
https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.sy...
]
Mark Struberg commented on CDI-392:
-----------------------------------
Pete what I mean is that if one Extension changes the AnnotatedType for a class in PAT,
and another Extension does as well, then depending on the order in which the Extensions
get invoked they see different AnnotatedTypes. We cannot prevent such side effects. But
this is fundamentally different to calling getBeans before the class scanning is finished
(which really is nonsense and we are right in preventing this).
I've updated my pull request accordingly.
Clarify when the operations of BeanManager can be called
--------------------------------------------------------
Key: CDI-392
URL: https://issues.jboss.org/browse/CDI-392
Project: CDI Specification Issues
Issue Type: Clarification
Reporter: Matus Abaffy
Assignee: Mark Struberg
Labels: CDI_spec_chge, Ready_to_fix
Fix For: 1.2 Proposed
The current version of spec. states (under 11.3. The BeanManager object): "Any
operation of BeanManager may be called at any time during the execution of the
application."
This sentence is likely to be misinterpreted (see WELD-1453). Pointing out that
BeanManager's methods can be called (without causing exception) just after
AfterDeploymentValidation event is fired might be helpful.
--
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