Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Whats a naming service?  RSS feed

 
vijay kumar
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi guys,
am a novice in this area and am looking forward to know about java naming service (jndi) & other services (ldap for example)and how it fits into overall application scenario. could someone share a word or some link on that.
thanks
vijay
 
Andrew Shafer
Ranch Hand
Posts: 338
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I think most people are using LDAP in authentication schemes.
In theory JNDI (java version of LDAP more or less) or LDAP directories could be used for almost anything that a database is used for. This is especially true if the information in going to be read more often than it will be changed. For example, phone lists, address books, rate constants of chemical reactions, etc.

I believe there are certain advantages the directory offers in the types of objects that can be stored, the JNDI allows you to store and retrieve JAVA objects.
(http://java.sun.com/products/jndi/tutorial/ldap/models/index.html) compares JNDI to the LDAP model
search google.com for LDAP discussions, they are plentiful
Andrew
 
Frank Carver
Sheriff
Posts: 6920
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A naming service is a shared persistent repository, typically available to a group of applications or systems. LDAP comes from the need for a business to keep centralized mailing lists and addressbooks for all users. LDAP stands for Lightweight Directory Access Protocol. LDAP servers are usable by most modern email clients, for example, instead of or in addition to a local address book.
JNDI is a Java API which simplifies access to a whole range of things which might be considered as naming or directory services. JNDI can provide access to LDAP servers, but also to login and user information using YP/NIS and machine and network information using DNS. It has a pluggable architecture and allows "providers" to be developed for any similar information source.
One major use for JNDI these days is for storing configurations and parameters for J2EE systems. It is strongly suggested in all the EJB documentation to look up the details of EJBs in a JNDI directory, for example.
 
Tushar Kansara
Ranch Hand
Posts: 38
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JNDI is indeed come as panacea for the simple reason that it provides standard APIs for accessing different protocols be it LDAP or others.
if I were to quote a analogy, its something similar to the way java has turned Application Server market upside down. What they have done is they have defined Specifications for an Server Side Component. It is upto Vendors to implement the Specification, But for a Developer It does not matter how is the specs implemented what he is concerned about is a Standard API for accessing these services.
Similarly JNDI is a API which will allow developers to access the LDAP protocols and others without bothering about its implementation by the Vendors.
Regards
Tushar Kansara

------------------
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!