[cdi-dev] [JBoss JIRA] (CDI-716) Allow to recognize custom Bean at runtime
Antoine Sabot-Durand (JIRA)
issues at jboss.org
Thu Oct 12 05:33:00 EDT 2017
[ https://issues.jboss.org/browse/CDI-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Sabot-Durand updated CDI-716:
-------------------------------------
Fix Version/s: 2.1 (Discussion)
> 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
> Fix For: 2.1 (Discussion)
>
>
> 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.5.0#75005)
More information about the cdi-dev
mailing list