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

Extension disqualifies a jar as 'implicit bean archive'?

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Minor
    • None
    • None
    • None
    • None

    Description

      The bean-discovery-wording is a bit odd.
      This has been in since CDI-1.1

      An archive which:
      • contains a beans.xml file with the bean-discovery-mode of none, or,
      • contains an extension and no beans.xml file is not a bean archive.
      is not a bean archive.
      

      That means even if you have an @ApplicationScoped MyService class in a jar which has a single CDI Extension then this MyServices will not get picked up as CDI bean? At least according to this wording?
      Feels mega-weird to me and might conflict with the implicit beans archive definition a few lines below.

      I'm pretty sure in OWB we will pick those beans up. How does Weld behave?

      Attachments

        Issue Links

          Activity

            Public project attachment banner

              context keys: [headless, issue, helper, isAsynchronousRequest, project, action, user]
              current Project key: CDI

              People

                Unassigned Unassigned
                struberg Mark Struberg
                Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: