[cdi-dev] [JBoss JIRA] (CDI-456) fix Bean#getBeanClass() definition
Mark Struberg (JIRA)
issues at jboss.org
Thu Sep 4 08:08:00 EDT 2014
[ https://issues.jboss.org/browse/CDI-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12998837#comment-12998837 ]
Mark Struberg commented on CDI-456:
Sorry, seems my explanation was too brief ;)
Imagine you have an EAR with 3 WARs. Each of the WAR files add a Bean with the same class (which is in a shared ear lib), but with different bean attributes and different content.
The beanclass would be the same for all the 3 Bean<T>, but they are still in 3 totally different EE modules.
What means getBeanClass() is not usable to distinct the EE modules.
> fix Bean#getBeanClass() definition
> Key: CDI-456
> URL: https://issues.jboss.org/browse/CDI-456
> Project: CDI Specification Issues
> Issue Type: Bug
> Components: Beans
> Reporter: Mark Struberg
> currently Bean#getBeanClass() is defined to return the class of the bean it produces but has one important exception: in case of a producer method or field it must return the class of the owner bean of this method or field.
> Imo this only causes troubles and doesn't add any benefit.
> * At the time when 'using' the Bean (create and destroy) we always ONLY need the type which is to be created.
> * At the time we create interceptors we ONLY need the type which is to be created;
> * At the time we create the normalscoping proxies we ONLY need the type which is to be created;
> In fact the only time we need the ownerBean is when scanning the methods and fields in it. And for creating we really need the owner-Bean and not it's bean-class!
> In OWB we worked around this by having our own method getReturnType() which consistently returns the type which gets created.
This message was sent by Atlassian JIRA
More information about the cdi-dev