[weld-issues] [JBoss JIRA] Commented: (WELD-335) RIBean needs new definition of equality
[
https://jira.jboss.org/jira/browse/WELD-335?page=com.atlassian.jira.plugi...
]
Stuart Douglas commented on WELD-335:
-------------------------------------
The issue is no so much that other people are re-using RIBean, it is that if you use the
BeforeBeanDiscovery.addAnnotatedType() to add a bean multiple times with different
annotations it will not work, as the beans will have the same ID. This also means that you
cannot do addAnnoatedType() for a class in a bean discovery archive without vetoing the
discovered bean.
RIBean needs new definition of equality
---------------------------------------
Key: WELD-335
URL: https://jira.jboss.org/jira/browse/WELD-335
Project: Weld
Issue Type: Bug
Components: Class Beans (Managed and Session), Producers (Methods, Fields and
Disposers), Reflection layer
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Priority: Critical
Fix For: 1.0.1.CR1
Attachments: ri-bean-id-creator.patch, ri-bean-id-creator2.patch
Due to the implementation of equals/hashCode in RIBean only one ManagedBean is allowed
per underlying java class, so for example if you use the SPI to add two AnnotatedTypes
with the same underlying class but different qualifiers only one will get installed.
The following patch fixes this, would it be possible to get some feedback on it?
The AnnotatedTypeIdProvider class in the patch can also be used to implement meaningful
equlity for WeldAnnotated*
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira