118 to a context. There are no absolute roots.
 119 Therefore JNDI defines an <em>initial context</em>, 
 120 <code>InitialContext</code>,
 121 which provides a starting point for naming and directory operations.
 122 Once you have an initial context, you can use it to
 123 look up other contexts and objects.
 124 
 125 <h4>Exceptions</h4>
 126 
 127 JNDI defines a class hierarchy for exceptions that can be thrown in
 128 the course of performing naming and directory operations.  The root of
 129 this class hierarchy is <code>NamingException</code>.
 130 Programs interested in dealing with a particular exception
 131 can catch the corresponding subclass of the exception.
 132 Otherwise, programs should catch <code>NamingException</code>.
 133 
 134 
 135 <h2>Package Specification</h2>
 136 
 137 The JNDI API Specification and related documents can be found in the
 138 <a href="../../../technotes/guides/jndi/index.html">JNDI documentation</a>.
 139 
 140 @since 1.3
 141 
 142 </body>
 143 </html>

 118 to a context. There are no absolute roots.
 119 Therefore JNDI defines an <em>initial context</em>, 
 120 <code>InitialContext</code>,
 121 which provides a starting point for naming and directory operations.
 122 Once you have an initial context, you can use it to
 123 look up other contexts and objects.
 124 
 125 <h4>Exceptions</h4>
 126 
 127 JNDI defines a class hierarchy for exceptions that can be thrown in
 128 the course of performing naming and directory operations.  The root of
 129 this class hierarchy is <code>NamingException</code>.
 130 Programs interested in dealing with a particular exception
 131 can catch the corresponding subclass of the exception.
 132 Otherwise, programs should catch <code>NamingException</code>.
 133 
 134 
 135 <h2>Package Specification</h2>
 136 
 137 The JNDI API Specification and related documents can be found in the
 138 {@extLink jndi_overview JNDI documentation}.
 139 
 140 @since 1.3
 141 
 142 </body>
 143 </html>