org.apache.aries.jndi.legacy.support
Class LegacyInitialContextFinder

java.lang.Object
  org.apache.aries.jndi.legacy.support.LegacyInitialContextFinder

All Implemented Interfaces:

javax.naming.spi.InitialContextFactoryBuilder

public class LegacyInitialContextFinder
extends java.lang.Object
implements javax.naming.spi.InitialContextFactoryBuilder

Some OSGi based server runtimes, such as jetty OSGi and virgo rely on the thread context classloader to make their JNDI InitialContextFactory's available in OSGi, rather than relying on the OSGi JNDI spec. This is a little bizare, but perhaps is just a point in time statement. In any case to support them using Aries JNDI we have this ICFB which uses the Thread context classloader. We don't ship it in the jndi uber bundle because it is only for these runtimes which haven't caught up with the latest OSGi specs. Normally we want to enourage the use of the OSGi spec, but this is a backstop for those wanting to use Aries JNDI and one of these runtimes.

Constructor Summary

LegacyInitialContextFinder()

Method Summary

javax.naming.spi.InitialContextFactory

createInitialContextFactory(java.util.Hashtable<?,?> environment)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

LegacyInitialContextFinder

public LegacyInitialContextFinder()

Method Detail

createInitialContextFactory

public javax.naming.spi.InitialContextFactory createInitialContextFactory(java.util.Hashtable<?,?> environment)
                                                                   throws javax.naming.NamingException

Specified by:

createInitialContextFactory in interface javax.naming.spi.InitialContextFactoryBuilder

Throws:

javax.naming.NamingException