[ https://issues.jboss.org/browse/CDI-456?page=com.atlassian.jira.plugin.sy... ] Jozef Hartinger commented on CDI-456: ------------------------------------- {quote}jozef, how should that work? The 3 beans are different but have the same beanClass(). So how should this get implemented?{quote} Look at the example again. They do not have the same bean class. If they had the same bean class then that would be a bug. {quote} So what? Where in this sentence does it state that the 'bean class of the bean' cannot be null? It neither does define what the 'bean class of the bean' is used for by the container. oh fine, but this is not about Alternatives! Show me one single line where you read that getBeanClass() must not be null for any custom bean. This is just missing from the spec and we should clarify what should happen in this case. {quote} Very weird logic you are using here. {{BeanManager.fireEvent()}} does not specify that you cannot pass null, either. Yet, we can probably agree that calling {{BeanManager.fireEvent(null)}} is a stupid thing to do. Here, the spec clearly says that for a custom bean, CDI will call getBeanClass() to infer several pieces of information about the bean yet you feel that returning null is alright? -- This message was sent by Atlassian JIRA (v6.3.1#6329)