[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-8017) No bean is eligible for @Inject BeanManager manager;

Alexey Kazakov (JIRA) jira-events at lists.jboss.org
Wed Dec 29 13:55:17 EST 2010


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

Alexey Kazakov commented on JBIDE-8017:
---------------------------------------

There is BeanManagerImpl class In Weld which should be eligible for @Inject BeanManager manager;
I guess we should find the first non-abstract implementation of BeanManager interface and treat it as built-in Bean Manager bean.

> No bean is eligible for @Inject BeanManager manager;
> ----------------------------------------------------
>
>                 Key: JBIDE-8017
>                 URL: https://issues.jboss.org/browse/JBIDE-8017
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdi (jsr-299)
>    Affects Versions: 3.2.0.CR1
>            Reporter: Alexey Kazakov
>            Assignee: Viacheslav Kabanovich
>             Fix For: 3.2.0.CR1
>
>
> See the spec.:
> 11.3. The BeanManager object
> Portable extensions sometimes interact directly with the container via programmatic API call. The interface javax.enterprise.inject.spi.BeanManager provides operations for obtaining contextual references for beans, along with many other operations of use to portable extensions. The container provides a built-in bean with bean type BeanManager, scope @Dependent and qualifier @Default.
> The builtin implementation must be a passivation capable dependency, as defined in Section 6.6.2, "Passivation capable dependencies". Thus, any bean may obtain an instance of BeanManager by injecting it:
> @Inject BeanManager manager;

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list