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

Clarify whether SeContainerInitializer#disableDiscovery() also disables automatic CDI Extension pickup

    Details

    • Type: Clarification
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 2.0.SP1
    • Fix Version/s: None
    • Component/s: Portable Extensions
    • Labels:
      None

      Description

      The wording in SeContainerInitializer is a bit ambiguous whether CDI Extensions should still automatically get detected if SeContainerInitializer#disableDiscovery() got called.
      The spec just talks about "internal synthetic bean archive".
      And the JavaDoc says "By default, the discovery is enabled so that all beans from all discovered bean archives are considered." So again also just beans.
      Both wordings give the impression that CDI Extensions (which don't use scanning but java.util.ServiceLoader) might still work.

      Otoh the JavaDoc contains the sentence "Moreover, it's also possible to disable the discovery completely so that only the "synthetic" bean archive is considered:" which contains "disable the discovery completely".

      Both options are fine for me, but in hindsight of portability it might be wise to clarify it.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                struberg Mark Struberg
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: