Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11817

CDI @Resource(lookup=...) processing does not start corresponding binder service

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 25.0.0.Beta1
    • 16.0.0.Final
    • CDI / Weld
    • None
    • Workaround Exists
    • Hide

      Use a <resource-ref/> which references a <lookup-name/> via a <res-ref-name/> , and use @Resource(name = "...") instead.

      Show
      Use a <resource-ref/> which references a <lookup-name/> via a <res-ref-name/> , and use @Resource(name = "...") instead.

    Description

      If the corresponding binding service (the service responsible for creating the jndi binding) is not ACTIVE (e.g. clustering binding services are always PASSIVE) or, due to a race condition, has not yet started completely, a null value will be returned.
      The ee subsystem processes @Resource(lookup=...) correctly by establishing a dependency on the corresponding binder service.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-22290 [GSS](7.4.z) WFLY-11817 - CDI @Resource(lookup=...) processing does not start corresponding binder service

          • 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.
          • Verified

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: