[ https://issues.jboss.org/browse/CDI-10?page=com.atlassian.jira.plugin.sys... ] Antoine Sabot-Durand commented on CDI-10: ----------------------------------------- I think there are mixed needs here. And as we have tickets exposing similar needs (CDI-562, CDI-561and CDI-515), I think interesting to start from use cases. I see 2 of them (please add others if I missed one): # Getting class of the bean to "read" meta-data. IMO in this case accessing the class is not the best solution: meta-data may have been overridden and as section 11.4 states : {quote}The container must use the operations of Annotated and its subinterfaces to discover program element types and annotations. The container must not directly call the Java Reflection API{quote} # Getting the actual unwrap instance to have an unmanaged version of the instance (as described in CDI-561). But the use case are less obvious and the fact that other proxies may be injected in the instance make this rather hard to specify. If we focus on 1st use case (having a way to read meta-data). We have to provide a way to retrieve the {{Bean}} from the instance and add a way to easily discover the nature of a given {{Bean}} (managed bean, session, bean, producer, custom). Having this info will help user to know where to find meta-data... Regarding second point, every body interested should describe a user case from user POV to see if it's worth digging in that direction. -- This message was sent by Atlassian JIRA (v6.4.11#64026)