[cdi-dev] [JBoss JIRA] (CDI-392) Clarify when the operations of BeanManager can be called

[Mark Struberg (JIRA)]

    [ https://issues.jboss.org/browse/CDI-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12957534#comment-12957534 ] 

Mark Struberg commented on CDI-392:
-----------------------------------

Well, we have this behaviour throughout the whole container. It's also not guaranteed in which order different Extensions get the ProcessAnnotatedType called for example. Nor any other CDI Extension event. But this is fundamentally different to the bean-scanning randomness which is totally unpredictable.
                
> 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