[cdi-dev] [JBoss JIRA] Commented: (CDI-113) Add some design time readable metadata for built-in beans of CDI-implementations.

[ https://issues.jboss.org/browse/CDI-113?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on CDI-113: ------------------------------- bq. Nothing limits CDI container to have a few implementation in class path but use the only one (at least at once). For runtime it's not a problem. You know that you must provide a BeanManager and you provide it. But what if the developer added the following class in the classpath (I don't know why he might do it): bq. public class MyNotUsedBeanManagerImplimentation implements BeanManager { ... } bq. Runtime still works since this dead code is not used by CDI container but how tools can know that there is some difference between those BeanManager implementations? bq. Agree that may be this example is too tricky. And for 99.9% there will be the only implementation for every required service. But I just wanted to show that what is obvious for runtime is not so for design time. Alexey, can you give example of why tools needs to know this - how would it represent this info to the user? bq. Second problem may be more important. Even if we know for sure that there is the only one BeanManager implementation, the only one UserTransaction implementation, etc. we should scan every jar in the class path since we don't have any marker like beans.xml to skip not-CDI jars. It may be too long I don't understand this problem, why do you need to do this? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira