[
https://issues.jboss.org/browse/WFLY-1727?page=com.atlassian.jira.plugin....
]
Eduardo Martins commented on WFLY-1727:
---------------------------------------
[~jmartisk] do you think it's worth to force external contexts to be bound in a
specific context, for instance java:external/ or java:jboss/external/, so resource
injection can identify and setup the lookup with a dependency only to the external context
root context, no matter the lookup name is a child resource of it? An example, resource
injection for java:jboss/external/ldap-x/dc=jboss,dc=org would setup a dependency only for
java:jboss/external/ldap-x
Allow injection of resources from external JNDI contexts
--------------------------------------------------------
Key: WFLY-1727
URL:
https://issues.jboss.org/browse/WFLY-1727
Project: WildFly
Issue Type: Feature Request
Components: Naming
Reporter: Jan Martiska
Assignee: Eduardo Martins
The ability to federate external JNDI contexts into WildFly's JNDI namespaces was
introduced with WFLY-287.
Currently, it is not possible to programatically inject resources into applications (eg.
using @Resource annotation) from the federated contexts. It would be a nice to have
feature.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira