[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=12948228#comment-12948228 ] 

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

Well, there is nothing in the API which says that this is optional for the BeanManager. 

We usually use the wording 'non-portable behaviour results' for parts which does exactly that. But in the case of calling getBeans during the build-up of the Beans itself it's not non-portable but it's really just broken due to the randomness of the bean-discovery order. This has nothing to do with non-portable but really is broken. This is hardly detectable by junior developers as it is similar to concurrency issues in such that it appears randomly.
                
> 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