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

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

XMLWordPrintable

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

      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.

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

                Created:
                Updated:
                Resolved: