[cdi-dev] [JBoss JIRA] (CDI-700) BeanManager.createInstance() shouldn't be allowed before AfterDeploymentValidation
Matej Novotny (JIRA)
issues at jboss.org
Wed Apr 5 09:55:00 EDT 2017
[ https://issues.jboss.org/browse/CDI-700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13389396#comment-13389396 ]
Matej Novotny commented on CDI-700:
-----------------------------------
I, on the other hand, fully agree.
Current state doesn't make sense and this issue looks like a mere overlook in the spec/doc.
{{BeanManager.getReference}} should have the same limitations as {{BeanManager.createInstance}} as they can be used in similar manner.
I would be weird if you could use one but were prohibited from using the other to achieve the same goal.
After all {{BeanManger.createInstance}} is a sort of shorcut from having to create creational context, bean attributes, bean itself and then getting a reference.
> 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
>
> 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