Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-106

Bean manager resolve() doesn't take specialization into account

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 1.0.0.CR1
    • 1.0.0.PREVIEW1
    • None
    • None

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

            pmuiratbleepbleep Pete Muir (Inactive)
            drallendc@gmail.com David Allen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: