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

BeanManager#getBeans() shall throw an Exception if called before AfterDeploymentValidation

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.1.FD
    • 1.1.EDR
    • Beans

    Description

      We recently had the erroneous case in DeltaSpike that an Extension did call BeanManager#getBeans() in an @Observes ProcessBean method.

      Doing so leads to random behaviour as the result of getBeans() depends on the order in which the other beans got processed already. E.g. getBeans(Object.class) will return an empty list for the first bean getting processed, and will return all beans -1 for the last bean. That just makes no sense and will create unreproducible bugs.

      PROPOSAL:
      We shall add spec language to BeanManager#getBeans() that any invocation before the AfterDeploymentValidation phase will result in a deployment error.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. CDI-315 Allow BeanManager methods, such as getBeans in AfterDeploymentValidation observers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. CDITCK-320 Test that certain BeanManager methods cannot be called during application init

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. WELD-1274 Check that certain BeanManager methods are not called at bootstrap

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Clarification - A clarification needed to a specification based on community feedback CDI-392 Clarify when the operations of BeanManager can be called

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: