[ https://jira.jboss.org/jira/browse/WBRI-331?page=com.atlassian.jira.plugi... ] Pete Muir updated WBRI-331: --------------------------- Summary: Bean manager resolve() doesn't take specialization into account (was: Bean manager resolve() still uses deployment types) Description: 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() was:The resolve() method is still using deployment types 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." -- 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