[webbeans-issues] [JBoss JIRA] Closed: (WBRI-331) Bean manager resolve() doesn't take specialization into account

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/jira/browse/WBRI-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed WBRI-331.
--------------------------

    Resolution: Done
      Assignee: Pete Muir


> Bean manager resolve() doesn't take specialization into account
> ---------------------------------------------------------------
>
>                 Key: WBRI-331
>                 URL: https://jira.jboss.org/jira/browse/WBRI-331
>             Project: Web Beans
>          Issue Type: Bug
>    Affects Versions: 1.0.0.PREVIEW1
>            Reporter: David Allen
>            Assignee: Pete Muir
>             Fix For: 1.0.0.CR1
>
>
> The resolve() method take specialization into account to distinguish between ambiguous beans.  Section 5.3.1 states what this method should do.  The test in org.jboss.jsr299.tck.tests.extensions.beanManager.BeanManagerTest::testAmbiguousDependencyResolved() currently attempts to use specialization with both the specializing and the specialized beans in the set to resolve().  The method should do the following in this case:  "The container eliminates all matching beans that are specialized by some other matching bean."
> Also
> org.jboss.jsr299.tck.tests.lookup.byname.ResolutionByNameTest.testAmbiguousELNamesResolved()

-- 
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