[cdi-dev] [JBoss JIRA] (CDI-716) Allow to recognize custom Bean at runtime

[Antoine Sabot-Durand (JIRA)]

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

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

Agree to go that way. IMO it would be better to add {{getKind()}} and know the exact bean kind (Managed, EJB, Producer, Custom, Built-in)

> Allow to recognize custom Bean at runtime
> -----------------------------------------
>
>                 Key: CDI-716
>                 URL: https://issues.jboss.org/browse/CDI-716
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Beans
>    Affects Versions: 2.0 .Final
>            Reporter: Matej Novotny
>
> At the moment, they only way to tell custom bean (created via {{BeanConfigurator}} or class implementing {{javax.enterprise.inject.spi.Bean}}) from "standard" one is to have an extension and listen to {{ProcessSyntheticBean}}. This is good enough if it's sufficient to tell the difference at bootstrap time.
> However, at runtime, there is no way to do this.
> We could add a method to {{javax.enterprise.inject.spi.Bean}} which would allow to tell the difference. The name of the method could be {{isCustom()}} or {{getKind()}}.
> Generally, there should be no need to differentiate between custom/standard beans, but when digging deeper, it doesn't hurt to know. Putting this into {{Bean}} interface keeps it deep enough while still giving the information.
> One of the use cases for this would be CDI-194, which could be "nicely" implemented (avoiding {{null}} values), if there was a way to recognize custom bean.



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