[cdi-dev] [JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation

Antoine Sabot-Durand (JIRA) issues at jboss.org
Wed Apr 5 11:07:00 EDT 2017


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

Antoine Sabot-Durand commented on CDI-700:
------------------------------------------

During 1.2 discussion we decided to allow some {{BeanManager}} methods to be called during {{AfterBeanDiscovery}} observer invocation. These was not allowed in CDI 1.1.
But as Martin said, we agreed that {{getReference}} and {{getInjectablereference}} couldn't be called before {{AfterDeploymentValidation}}. As createInstance() provides something similar, I find consistent to limit its usage in the same way. The rule being: you can't request a bean instance before {{AfterDeploymentValidation}}. That makes sense since custom context are registered with this observer.

> BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation
> ----------------------------------------------------------------------------------
>
>                 Key: CDI-700
>                 URL: https://issues.jboss.org/browse/CDI-700
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>            Reporter: Antoine Sabot-Durand
>             Fix For: 2.0 .Final
>
>
> Spec doesn't say anything about it and javadoc allows its usage in {{AfterBeanDiscovery}} observers.
> The method should also be listed in section 11.3 related to {{BeanManager}}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the cdi-dev mailing list