[weld-issues] [JBoss JIRA] (WELD-1075) Ambiguous dependencies when only one correct dependency exists

[Ales Justin (JIRA)]

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

Ales Justin commented on WELD-1075:
-----------------------------------

What about doing this as a GitHub pull-request? :-)
(but np if not, big thanks already -- it would just speed-up things ...)
                
> Ambiguous dependencies when only one correct dependency exists
> --------------------------------------------------------------
>
>                 Key: WELD-1075
>                 URL: https://issues.jboss.org/browse/WELD-1075
>             Project: Weld
>          Issue Type: Bug
>          Components: Resolution (Typesafe and by Name)
>    Affects Versions: 1.1.1.Final, 1.1.4.Final
>            Reporter: Sebastian Graca
>         Attachments: testcase-arquillian.zip, testcase.zip
>
>
> Running attached application gives the error:
> WELD-001409 Ambiguous dependencies for type [Interface1<UUID, String>] with qualifiers [@Default] at injection point [[field] @Inject private test.Bean.dependency]. Possible dependencies [[Managed Bean [class test.ConcreteClass1] with qualifiers [@Any @Default], Managed Bean [class test.ConcreteClass2] with qualifiers [@Any @Default], Managed Bean [class test.ConcreteClass3] with qualifiers [@Any @Default]]]
> But only ConcreteClass3 has required type of Interface1<UUID, String>
> When ConcreteClass1 and ConcreteClass2 extens AbstractClass1 instead of AbstractClass2 everything works as expected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira