65 and intuitive for the Java programmer.
  66 For example, when looking up a printer name from the directory,
  67 it is natural for you to expect to get
  68 back a printer object on which to operate.
  69 
  70 
  71 <h4>Multiple Naming Systems (Federation)</h4>
  72 
  73 JNDI operations allow applications to supply names that span multiple
  74 naming systems.  So in the process of completing
  75 an operation, one service provider might need to interact
  76 with another service provider, for example, to pass on
  77 the operation to be continued in the next naming system.
  78 The service provider package provides support for
  79 different providers to cooperate to complete JNDI operations.
  80 
  81 
  82 <h2>Package Specification</h2>
  83 
  84 The JNDI SPI Specification and related documents can be found in the
  85 <a href="../../../../technotes/guides/jndi/index.html">JNDI documentation</a>.
  86 
  87 @since 1.3
  88 
  89 </body>
  90 </html>

  65 and intuitive for the Java programmer.
  66 For example, when looking up a printer name from the directory,
  67 it is natural for you to expect to get
  68 back a printer object on which to operate.
  69 
  70 
  71 <h4>Multiple Naming Systems (Federation)</h4>
  72 
  73 JNDI operations allow applications to supply names that span multiple
  74 naming systems.  So in the process of completing
  75 an operation, one service provider might need to interact
  76 with another service provider, for example, to pass on
  77 the operation to be continued in the next naming system.
  78 The service provider package provides support for
  79 different providers to cooperate to complete JNDI operations.
  80 
  81 
  82 <h2>Package Specification</h2>
  83 
  84 The JNDI SPI Specification and related documents can be found in the
  85 {@extLink jndi_overview JNDI documentation}.
  86 
  87 @since 1.3
  88 
  89 </body>
  90 </html>