You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Phil Steitz (JIRA)" <di...@incubator.apache.org> on 2005/03/27 21:37:16 UTC
[jira] Resolved: (DIRNAMING-15) Add support for "jndi urls" - to support federation across named contexts
[ http://issues.apache.org/jira/browse/DIRNAMING-15?page=history ]
Phil Steitz resolved DIRNAMING-15:
----------------------------------
Resolution: Fixed
> Add support for "jndi urls" - to support federation across named contexts
> -------------------------------------------------------------------------
>
> Key: DIRNAMING-15
> URL: http://issues.apache.org/jira/browse/DIRNAMING-15
> Project: Directory Naming
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira