[ https://issues.jboss.org/browse/CDI-562?page=com.atlassian.jira.plugin.sy... ] Martin Kouba commented on CDI-562: ---------------------------------- I think there are two similar open issues which might offer a better solution for this use case: # CDI-515 - allow to obtain Bean metadata from {{javax.enterprise.inject.Instance}}, so that if a user wants to get the metadata the programmatic lookup would help # CDI-10 - if we introduce a marking interface for client proxies, e.g. {{BeanProxy}}, we could also probably add {{getBean()}} method I'm not so sure it's a good idea to add a method to the BeanManager. Let's have the following producer: {code:java} clas FooProducer { @Alpha // qualifier @Produces Foo produceAlphaFoo() { ... } @Bravo // qualifier @Produces Foo produceBravoFoo() { ... } } {code} How to identify a bean for any {{Foo}} instance? We would have to use some internal construct even for contextual instances of dependent beans with no interceptors/decorators. And that's not possible - such a bean does not have to be proxyable. Or am I missing something? -- This message was sent by Atlassian JIRA (v6.4.11#64026)