LDAP Controls via Java and JNDI
Java Naming and Directory Interface (JNDI) provides access to different kinds of naming and directory services. It offers a common interface to connect to several naming services, including RMI , CORBA, DNS, LDAP servers, file systems and even the Windows registry. This article demonstrates standard components (J2SE 5.0), as well as custom application development methods.
The role of JNDI in J2EE
Mastering J2EE can be daunting, with an ever-growing list of technologies and acronyms. The Java Naming and Directory Interface (JNDI) has been at the core of the Java 2 Platform, Enterprise Edition (J2EE) from its inception, but it is often underutilized by novice J2EE developers. This article will help demystify the role of JNDI in J2EE applications and show how it can help decouple your application from the details of deployment.
Use JNDI to share objects between different virtual machines
Imagine the following: Process A on machine B puts an object into a Hashtable. Now, a separate process C on a different machine D can access that object from its own local copy of the Hashtable -- even after process A terminates and the virtual machine unloads! Now imagine all this is achieved without the use of RMI, and without involving an ORB, CORBA, EJB, or a database. What's the secret? The Java Naming and Directory Interface (JNDI). This month's tool is the JNDIHashtable -- which, as its name reveals, uses JNDI to do its thing.
Network World, an International Data Group publication, is the industry's only newsweekly shaping the future of network computing in the enterprise.
subscribe now
