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

Pete Muir (JIRA) issues at jboss.org
Sat Mar 29 13:02:13 EDT 2014


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

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

I'm ok with this change, but I think we then need some warning on the method, that if called before ADV, you will not see the complete set of beans, as there is no guarantee about which order ABD methods are called in, and we add a FAQ indicating you can wreck startup times with this method, if used irresponsibly.
                
> 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


More information about the cdi-dev mailing list