[ https://issues.redhat.com/browse/WFLY-12835?page=com.atlassian.jira.plugi... ] charles ghislain commented on WFLY-12835: ----------------------------------------- This seems related to WFLY-12811 and commit https://github.com/wildfly/wildfly/commit/4f3bc4754216136e19470bdd3a84124.... The [DeploymentProcessor|https://github.com/wildfly/wildfly/blob/5bad8de7386fe...] registers a CDIExtension instance for each deployment (sub)module, but only the last one is preserved as only one instance of each extension type may be registered ([WeldPortableExtensions javadoc|https://github.com/wildfly/wildfly/blob/64debb7134598bebb03fccf55...]). However, by only registering the extension on parent modules (ei skipping wars when inside ears), the config property is not injected as reported in WFLY-12811. The real issue seems to be in the [AfterDeploymentValidation listener|https://github.com/wildfly/wildfly/blob/8b321779c6bc17a44f699705...], as the injected BeanManager does not resolve healthchecks in the war inside an ear. Strangley, `InitialContext.doLookup("java:comp/BeanManager")` throws a NameNotFoundException there, while `CDI.current().getBeanManager()` returns a beanManager suitable to resolve all healthchecks. I edited [MicroProfileHealthTestBase|https://github.com/cghislai/wildfly/blob/mp-he...] to deploy the war in an ear. Using that change, test fails because of "Required property org.wildfly.test.integration.microprofile.health.MyProbe.propertyConfiguredByTheDeployment not found", but the probes seem correctly resolved. -- This message was sent by Atlassian Jira (v7.13.8#713008)