Home > Articles

  • Print
  • + Share This
This chapter is from the book

Using JNDI Functionality

You have already seen the most common use of JNDI within the J2EE environment and that is the lookup of objects, usually J2EE components. JNDI can also be used to:

  • Bind objects to the name service

  • List objects in a context

  • Create and delete contexts

These features are briefly discussed in the following sections.

CAUTION

One word of warning about the security features discussed: Some Name Services (such as LDAP) may use security features to ensure that only authorized programs can change the object bindings or contexts. On a live system, the program must supply valid user credentials when obtaining the initial context (see the "Security" section later in this lesson). If you attempt to modify an existing name or bind a new name without the requisite permissions, a javax.naming.NoPermissionException is thrown. The "Security" section of today's lesson covers this in more detail.

Binding and Renaming Objects

Binding an object means adding a name to the Name Service and associating that name with a Java object. The name and object are bound to a context using the Context.bind() method. The object to be bound must implement the Serializable interface so that the name server can store a copy of the object.

NOTE

There is a way of binding objects that does not require the class to implement the Serializable interface. A class can implement the javax.naming.Referenceable interface instead; this is quite specialized and outside the scope of this chapter (this interface is described in the JNDI Tutorial from Sun Microsystems, see http://java.sun.com/products/jndi/tutorial/).

The following code fragment taken from Day 19 shows how to bind an RMI-IIOP server (HelloUserImpl) against the name HelloUser:

HelloUserImpl hui = new HelloUserImpl();
Context ctx = new InitialContext();
ctx.rbind("HelloUser",hui);

If an object is already bound to that name, the Context.bind() method will fail with a NameAlreadyBoundException (which extends NamingException). The method Context.rebind() will unbind any currently bound object before binding the new object.

A Service Provider may not support binding of all types of objects. If the service cannot bind a particular object, it will throw an exception. An exception is also thrown if an invalid name is used. Remember that different Service Providers may have different naming conventions.

An object can be unbound using Context.unbind(), for example:

Context ctx = new InitialContext();
ctx.unbind("HelloUser",hui);

You can rename objects using Context.rename() by specifying the old name and then the new name as parameters.

ic.rename("HelloUser","SayHello");

The new name must specify a name in the same context as the old name. An object must be bound to the old name, and the new name must not have a bound object or else a NamingException is thrown.

Changing Contexts

So far you have used the default context returned by the InitalContext constructor. Often you can simplify name look up or improve performance by changing contexts.

J2EE components may find it convenient to change contexts to the Java Component Environment before looking up DataSource objects or EJB references.

Use the Context.lookup() method to look up a sub-context and then use the return Context object for future lookups. For example:

Context ic = new InitialContext();
Context ctx = (Context)ic.lookup("java:comp/env");
DataSource ds = (DataSource)ctx.lookup("jdbc/Agency");

This is particularly useful if you are doing multiple lookups within one context. The idea is much the same as changing directories in a file system when working within the same directory structure.

Listing Contexts

The namespace represents contexts as names, and you can look these up just like any other name. You can obtain a listing of the names in a context by using Context.list(). This method provides a list of name and class bindings as a javax.naming.NamingEnumeration, where each element in the enumeration is a javax.naming.NameClassPair object. Listing 3.2 shows a simple program to list the names and classes for the example sams sub context.

Listing 3.2 Full Text of JNDIList.java

import javax.naming.*;

public class JNDIList
{
 public static void main(String[] args)
 {
  try {
   Context ctx = new InitialContext();
   if (args.length == 0) {
    listContext (ctx,"");
   }
   else {
    for (int i=0; i<args.length; i++) 
     listContext (ctx,args[i]);
   }
  }
  catch (NamingException ex) {
   ex.printStackTrace();
   System.exit(1);
  }
 }
 
 public static void listContext (Context ctx, String subctx) 
  throws NamingException
 {
  System.out.println("Listing Context: "+subctx);
  NamingEnumeration list = ctx.list(subctx);
  while (list.hasMore())
  {
   NameClassPair item = (NameClassPair)list.next();
   String cl = item.getClassName();
   String name = item.getName();
   System.out.println(cl+" - "+name);
  }
 }
} 

The parameter to the list() method defines the name of the context to list. If this is the empty string, the method lists the current context.

Use the command

asant JNDList

to run this example program and enter a context, or list of contexts, when prompted. Initially just press return to get a listing of the default context, then try the jdbc context to see the entry for the jdbc/Agency DataSource you used earlier.

The Context.list() method returns the name and the bound object's classname, but not the object itself. It is a lightweight interface designed for browsing the namespace.

A second method, called Context.listBindings(), retrieves the object name, class name, as well as the object itself. This method invokes the extra run time cost of retrieving the object from the name. The listBindings() method also returns a NamingEnumeration, but this time each element is of type javax.naming.Binding. Access methods in the Binding class support retrieval of the information of the bound object.

Listing 3.3 shows a simple recursive tree-walking program that is a useful diagnostic tool for examining JNDI namespaces.

Listing 3.3 Full Text of JNDITree.java

import javax.naming.*;
public class JNDITree
{
 public static void main(String[] args) {
  Context ctx=null;
  try {
   ctx = new InitialContext();
   listContext (ctx,"");
  } 
  catch (NamingException ex) {
   System.err.println (ex);
   System.exit(1);
  }
 }

 private static void listContext (Context ctx, String indent) {
  try {
   NamingEnumeration list = ctx.listBindings("");
   while (list.hasMore()) {
    Binding item = (Binding)list.next();
    String className = item.getClassName();
    String name = item.getName();
    System.out.println(indent+className+" "+name);
    Object o = item.getObject();
    if (o instanceof javax.naming.Context)
     listContext ((Context)o,indent+" ");
   }
  }
  catch (NamingException ex) {
   System.err.println ("List error: "+ex);
  }
 }
}

Creating and Destroying Contexts

Binding a composite name will automatically create any intermediate sub-contexts required to bind the name. Binding the name such as

Day03/examples/jdbc/Agency 

creates the following sub-contexts if they don't already exist:

Day03
Day03/examples
Day03/examples/jdbc

you can explicitly create contexts with the Context.createSubcontext() method. The single method parameter is the name of the context. If this is a composite name, all intermediate contexts must already exist. The createSubContext() method will throw a NameAlreadyBoundException if the name already exists.

The Context.destroySubcontext() method can destroy contexts. Again, the single method parameter is the name of the context. The context does not have to be empty, because the method will remove from the namespace any bound names and sub-contexts with the destroyed context.

The destroyContext() method can throw a NameNotFoundException if the name doesn't exist and a NotContextException if the bound name is not a context.

Working with Multiple Name Services

You can specify a URL as a parameter to the Context lookup() and bind() methods. For example,

Context ic = new InitialContext();
Object obj = ic.lookup("ldap://localhost:389/cn=Winston,dc=my-domain,dc=com");

This overrides the default context and forces JNDI to perform the lookup against the specified server. You need to take care with this approach, because the CLASSPATH must contain the necessary Service Provider classes, and these must be able to process the request bind or lookup operation. In practice, this means that the URL must use the same Service Provider classes as the initial context.

JNDI Events

JNDI supports an event model similar to the event listeners in the Java AWT and Swing classes. However, the underlying JNDI Service Provider must also provide support for the event model for a client to register event handlers.

The javax.naming.event package supports two types of JNDI event listener (both are sub-classes of NamingListener):

  • NamespaceChangeListener reports on changes to the namespace objects that are added, removed, or renamed.

  • ObjectChangeListener reports on changes to an object when its binding is replaced (the object has been updated) or attributes are added, removed, or replaced.

Both interfaces define appropriate methods that are called when changes occur in the JNDI namespace. A javax.naming.event.NamingEvent object is passed to the listener method to define:

  • The type of event (for example, name added or object changed)

  • The name binding before the event occurred

  • The name binding after the event occurred

JNDI event handling provides an effective means for monitoring changes to a namespace to maintain up-to-date information about the registered objects.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020