[jboss-jira] [JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Matej Novotny edited comment on WFLY-11858 at 3/20/19 9:22 AM: --------------------------------------------------------------- bq. Would you have some clue for me how to get info on all the registered beans (which can be `@Inject`ed?) Hmm, first thing coming to mind is a CDI extension with observer for container lifecycle events (such as bean addition - {{ProcessBean}}, or producer method etc). [{{ProcessBean}}|http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#process_bean] is probably a good starting point as it triggers for every added bean, no matter if it is backed by class/producer method or added synthetically. bq. To your point about `new IntialContext()` I think it's not an issue as it's practice used on many places in the container and second there should be possibly one `JNDIBean` in container(?, I can be easily missing how the CDI handles this). Those are both good points, you are right :-) was (Author: manovotn): bq. Would you have some clue for me how to get info on all the registered beans (which can be `@Inject`ed?) Hmm, first thing coming to mind is a CDI extension with observer for container lifecycle events (such as bean addition - {{ProcessBean}}, or producer method etc). {{ProcessBean}} is probably a good starting point as it triggers for every added mean, no matter if it is backed by class/producer method or added synthetically. bq. To your point about `new IntialContext()` I think it's not an issue as it's practice used on many places in the container and second there should be possibly one `JNDIBean` in container(?, I can be easily missing how the CDI handles this). Those are both good points, you are right :-) -- This message was sent by Atlassian Jira (v7.12.1#712002)