 - JNDI (Java Naming and Directory Interface) enables Java platform-based applications to access multiple naming and directory services. Part of the Java Enterprise application programming interface (API) set, JNDI makes it possible for developers to create portable applications that are enabled for a number of different naming and directory services, including: file systems; directory services such as Lightweight Directory Access Protocol (LDAP), Novell Directory Services, and Network Information System (NIS); and distributed object systems such as the Common Object Request Broker Architecture (CORBA), Java Remote Method Invocation (RMI), and Enterprise JavaBeans (EJB).
As an illustration of what JNDI does, Todd Sundsted (in a JavaWorld article, JNDI overview, Part 1: An introduction to naming services) uses the analogy of a library's file system. Sundsted says that JNDI organizes and locates components within a distributed computing environment similarly to the way that card catalogs (and increasingly computer applications) organize and represent the locations of books within a library. A distributed application needs a means of locating components in the same way that the library patron needs a means of locating the book: just rummaging around inside a library - or an application - is not an efficient way to find a particular object. JNDI makes it possible for application components to find each other. Because different naming and directory service providers can be seamlessly connected through the API, Java applications using it can be easily integrated into various environments and coexist with legacy applications. The current version, JNDI 1.2, was specified with input from Netscape, Novell, Tarantella, Sun, and BEA. JNDI is considered an industry standard.
 |
Learn more about Java Web Services |
| JavaOne: JBoss on SOA middleware, Java EE and data services: Is SOA middleware that different from traditional middleware? At JavaOne, Red Hat's Craig Muzilla ponders that and the future of Java EE and data services. |
| Java One: Mule architect looks to bring REST to SOA: In a conversation at JavaOne, MuleSource's Dan Diephouse, talks about his work on Mule Galaxy, the REST-based open source registry/repository that is going GA later this month. |
| Mule architect sees REST with Atom rising, UDDI fading: Dan Diephouse, the creator of XFire and software architect at MuleSource Inc., discusses the advantages in using REST and the Atom Publishing Protocol. |
| Oracle links SOA, data services, BI and BAM: When it comes to incorporating data services, business intelligence (BI), and business activity monitoring (BAM), Oracle has not lost sight of its database roots. |
| Eclipse, Sun and Oracle team up on persistence API: The surprise announcement from EclipseCon, is Sun Microsystems. selecting the Oracle led EclipseLink project as the reference implementation for the Java Persistence API 2.0. |
| JavaOne news: A collection of SOA and Web services news related articles from the JavaOne conference held in San Francisco. |
| 2006 JavaOne coverage: A compilation of stories written about the JavaOne conference held in San Francisco this past May. |
| Chapter of the week: Security and Ajax: This chapter, excerpted from Ajax in Action, discusses security-related concerns that have particular implications for Ajax. |
| Chapter of the week: Working with Beehive Web services and JSR 181: This chapter, excerpted from Pro Apache Beehive, explores the Web service capabilities that are a part of Apache Beehive. You'll learn about JSR 181, Web Services Metadata for the Java ... |
| Decision time: .NET or J2EE?: How do .NET and J2EE stack up against one another? That depends on who you ask. We've compiled resources from both sides of the fence to help you decide for yourself. |
| CONTRIBUTORS: |
Cary MacWilliams |
| LAST UPDATED: |
04 Jul 2001
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
|
Show me everything on 
