]
Paul Ferraro updated WFLY-11817:
--------------------------------
Workaround Description: Use a <resource-ref/> which references a
<lookup-name/> via a <res-ref-name/> , and use @Resource(name =
"...") instead.
Workaround: Workaround Exists
CDI @Resource(lookup=...) processing does not start corresponding
binding service
---------------------------------------------------------------------------------
Key: WFLY-11817
URL:
https://issues.jboss.org/browse/WFLY-11817
Project: WildFly
Issue Type: Bug
Components: CDI / Weld
Affects Versions: 16.0.0.Final
Reporter: Paul Ferraro
Assignee: Matej Novotny
Priority: Major
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.
Compare this to the @Resource(lookup=...) processing in the ee subsystem, which correctly
establishes a dependency on the corresponding binder service.