Need JNDI example

I need a good example of a JNDI lookup for an oracle database. This is the code I have for getting the datasource however I still need to create the InitialContext. What do I put into the env hashtable?

What do I put into the env hashtable?

That depends on which naming provider you are using. Normally you'll find this in your Application Server documentation.

I'm looking to do a JNDI lookup for a JDBC connection for an Oracle 10i table. I'm using a JBoss app server. The current code I have is as follows

I guess too I was wondering where I put my xml file with all my attributes for the database. Tracing through the code, it looks as though its not being found.

In JBoss, the DataSource definition is deployed as a *-ds.xml file in the server's deploy directory.

Are you trying to do this lookup from client code, or from within an application deployed on the server?

From an application deployed on the server. It looks as though I have the JNDI names bound to the database. I know this because when JBoss comes up, it shows that in the console log. BUT when I do a lookup on the names it returns an exceptiom and gives me this.

When I step through the code and into the InitialContext class.. it fails on this method...

/**
 * Retrieves a context for resolving the string name <code>name</code>.
 * If <code>name</code> name is a URL string, then attempt
 * to find a URL context for it. If none is found, or if
 * <code>name</code> is not a URL string, then return
 * <code>getDefaultInitCtx()</code>.
 *
 * See getURLOrDefaultInitCtx(Name) for description
 * of how a subclass should use this method.
 * @param name The non-null name for which to get the context.
 * @return A URL context for <code>name</code> or the cached 
 * initial context. The result cannot be null.
 * @exception NoInitialContextException If cannot find an initial context.
 * @exception NamingException In a naming exception is encountered.
 * @see javax.naming.spi.NamingManager#getURLContext
 */
 protected Context getURLOrDefaultInitCtx(String name) 
throws NamingException {
if (NamingManager.hasInitialContextFactoryBuilder()) {
 return getDefaultInitCtx();
}
String scheme = getURLScheme(name);
if (scheme != null) {
 Context ctx = NamingManager.getURLContext(scheme, myProps);
 if (ctx != null) {
return ctx;
 }
}

Specifically this line...

which in turn goes here..

/***************** URL Context implementations ***************/
 
 /**
 * Creates a context for the given URL scheme id. 
 * 
 * The resulting context is for resolving URLs of the
 * scheme <code>scheme</code>. The resulting context is not tied
 * to a specific URL. It is able to handle arbitrary URLs with 
 * the specified scheme. 
 *
 * The class name of the factory that creates the resulting context 
 * has the naming convention scheme-idURLContextFactory 
 * (e.g. "ftpURLContextFactory" for the "ftp" scheme-id), 
 * in the package specified as follows.
 * The <tt>Context.URL_PKG_PREFIXES</tt> environment property (which
 * may contain values taken from applet parameters, system properties,
 * or application resource files)
 * contains a colon-separated list of package prefixes. 
 * Each package prefix in
 * the property is tried in the order specified to load the factory class.
 * The default package prefix is "com.sun.jndi.url" (if none of the
 * specified packages work, this default is tried).
 * The complete package name is constructed using the package prefix,
 * concatenated with the scheme id.
 *
 * For example, if the scheme id is "ldap", and the 
 * <tt>Context.URL_PKG_PREFIXES</tt> property
 * contains "com.widget:com.wiz.jndi",
 * the naming manager would attempt to load the following classes
 * until one is successfully instantiated:
 *<ul>
 * <li>com.widget.ldap.ldapURLContextFactory
 *<li>com.wiz.jndi.ldap.ldapURLContextFactory
 *<li>com.sun.jndi.url.ldap.ldapURLContextFactory
 *</ul>
 * If none of the package prefixes work, null is returned.
 *
 * If a factory is instantiated, it is invoked with the following
 * parameters to produce the resulting context.
 * 
 * <code>factory.getObjectInstance(null, environment);</code>
 * 
 * For example, invoking getObjectInstance() as shown above
 * on a LDAP URL context factory would return a
 * context that can resolve LDAP urls
 * (e.g. "ldap://ldap.wiz.com/o=wiz,c=us",
 * "ldap://ldap.umich.edu/o=umich,c=us", ...).
 *
 * Note that an object factory (an object that implements the ObjectFactory
 * interface) must be public and must have a public constructor that 
 * accepts no arguments.
 *
 * @param scheme The non-null scheme-id of the URLs supported by the context.
 * @param environment The possibly null environment properties to be 
 * used in the creation of the object factory and the context.
 * @return A context for resolving URLs with the 
 * scheme id <code>scheme</code>; 
 * <code>null</code> if the factory for creating the 
 * context is not found.
 * @exception NamingException If a naming exception occurs while creating
 * the context.
 * @see #getObjectInstance
 * @see ObjectFactory#getObjectInstance
 */
 public static Context getURLContext(String scheme,
Hashtable<?,?> environment)
throws NamingException
 {
// pass in 'null' to indicate creation of generic context for scheme
// (i.e. not specific to a URL).
 
 Object answer = getURLObject(scheme, null, null, null, environment);
 if (answer instanceof Context) {
return (Context)answer;
 } else {
return null;
 }
 }

environment is equal to an empty hashtable w/no key/value pairs in it and so answer is equal to null and thus returns null. And thus throws an exception. Specifically it throws this exception...

[ January 19, 2007: Message edited by: Dale DeMott ]

You need to specify the naming factory you are using. For JBoss4 that will be java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory. You'll also need the to include the URL for the naming provider, probably java.naming.provider.url=jnp://localhost:1099.

However, if you need to specify these environment values this suggest you are trying to lookup the DataSource from a remote client. If you are be aware this is only possible from JBoss4 and you need to configure your DataSource to allow this with <use-java-context>false</use-java-context> in the DS file.

Thanks much for your reply. Thats what I needed.