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

[Pete Muir (JIRA)]

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

Pete Muir commented on CDI-392:
-------------------------------

[~struberg] What I am saying is that people are *used* to getBeans() always returning the same thing, because it does most of the time (at runtime). So we should call out this difference. Start event order is always undefined, inside an event type.
                
> 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