You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <di...@incubator.apache.org> on 2009/05/06 18:27:30 UTC
[jira] Closed: (DIRNAMING-15) Add support for "jndi urls" - to
support federation across named contexts
[ https://issues.apache.org/jira/browse/DIRNAMING-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRNAMING-15.
--------------------------------------
> Add support for "jndi urls" - to support federation across named contexts
> -------------------------------------------------------------------------
>
> Key: DIRNAMING-15
> URL: https://issues.apache.org/jira/browse/DIRNAMING-15
> Project: Directory Naming
> Issue Type: Improvement
> Reporter: Phil Steitz
> Assignee: Phil Steitz
>
> Add support for "jndi urls" -- i.e., urls of the form "jndi:global/config/host" or even "jndi:app1/java:comp/env", where the first component of the name following the "jndi:" scheme identifier is the name of a named context. So, "jndi:global/config/host" refers to the entry named by "config/host" in the context named "global" in ContextBindings. To do this, add a jndiURLContextFactory sourcing SelectorJNDIContext instances, where SelectorJNDIContext extends and works like SelectorContext, but overrides getBoundContext to locate the bound context by name, rather than calling thread or classloader.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.