Uploaded image for project: 'CDI Specification Issues'
  1. CDI Specification Issues
  2. CDI-231

Clarify if Alternatives are filtered in BeanManager#getBeans() or #resolve()

    XMLWordPrintable

Details

    • Clarification
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • 1.0, 1.1.EDR
    • 1.1.PRD
    • Resolution
    • None

    Description

      The spec and javadoc are not really clear if the @Alternative filter defined in "5.2.1. Unsatisfied and ambiguous dependencies" is already performed in BeanManager#getBeans() or only later in BeanManager#resolve().

      Back in 2009 I did a blind test with an old Weld version which only returned @Alternatives in getBeans() and all other beans got filtered out. This seems to have changed now (since quite some time).

      Can we make this more clear what should happen in getBeans() and what should happen in resolve()?

      Attachments

        Activity

          People

            pmuiratbleepbleep Pete Muir
            struberg Mark Struberg
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: