[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... ] Ondra Chaloupka edited comment on WFLY-11858 at 3/21/19 5:36 AM: ----------------------------------------------------------------- [~manovotn] the condition is there because of https://issues.jboss.org/browse/JBTM-3044. Narayana was hard coded with {{InitialContext}} and the idea here was to allow Weld SE application to provide transaction manager as an injectable bean which is not dependent on the {{IntialContext}} lookup. For WFLY we need {{IntialContext}} for looking up while for Java SE app is right the opposite. [~ljnelson] I personally like what [~mkouba] affirmed. I understand the idea of the "user-supplied InitialContext bean implementations" but I don't think there is some reasonable demand for it. Or use what you proposed here: https://github.com/ochaloup/narayana/commit/964222d60c6f64849430057cd744d... But it's really a complicated code and I'm still not sure if there is somebody who like to provide the IntialContext as bean. was (Author: ochaloup): [~manovotn] the condition is there because of https://issues.jboss.org/browse/JBTM-3044. Narayana was hard coded with {{InitialContext}} and the idea here was to allow Weld SE application to provide transaction manager as an injectable bean which is not dependent on the {{IntialContext}} lookup. For WFLY we need {{IntialContext}} for looking up while for Java SE app is right the opposite. [~ljnelson] I personally like what [~mkouba] affirmed. I understand the idea of the "user-supplied InitialContext bean implementations" but I don't think there is some reasonable demand for it. -- This message was sent by Atlassian Jira (v7.12.1#712002)