[weld-issues] [JBoss JIRA] Commented: (WELD-335) RIBean needs new definition of equality

[Stuart Douglas (JIRA)]

    [ https://jira.jboss.org/jira/browse/WELD-335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12505511#action_12505511 ] 

Stuart Douglas commented on WELD-335:
-------------------------------------

I can do up a prototype in a couple of days, however on second thoughts I am not sure if this approach is a good idea. It adds a fair bit of complexity and fragility simply to maintain internal weld bean id's. 

What do you think?

> 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