As mentioned earlier in this lesson, the JNDI is defined
independent of any specific naming and directory service
implementation. This allows a variety of naming and directory
systems to be accessed in a common way. However, for it to offer
true independence, common policies are required that specify how
the naming and directory should be used. Without these policies,
you might be able to use the same API to access the data, but
how you find and use that data would still be directory-
dependent. The lack of policy is a problem not only for multiple
naming and directory systems, but also for single
naming/directory systems such as the LDAP. Without general
agreement on how the data in the directory is to be organized
and used, a single system can easily deteriorate into an
unmanageable mess. For example, suppose that two applications
need to associated data with a user in an enterprise. If each
application chooses its own policy of how to name and represent
a user in the directory, then the directory will conta