32 lines
2.7 KiB
HTML
32 lines
2.7 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Naming</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><a name="jndinam"></a>Naming</h5>
|
||
|
|
|
||
|
|
<p>Naming is used by WebSphere Application Server - Express applications and components to obtain references to objects they use.</p>
|
||
|
|
|
||
|
|
<p>These objects are bound into a mostly hierarchical structure, referred to as a name space. In this structure, all non-leaf objects are called contexts. Leaf objects can be contexts and other types of objects. Naming operations, such as lookups and binds, are performed on contexts. All naming operations begin with obtaining an initial context. You can view the initial context as a starting point in the name space.
|
||
|
|
</p>
|
||
|
|
|
||
|
|
<p>The name space structure consists of a set of name bindings, each consisting of a name relative to a specific context and the object bound with that name. For example, the name <tt>myApp/myDataSource</tt> consists of one non-leaf binding with the name <tt>myApp</tt>, which is a context. The name also includes one leaf binding with the name <tt>myDataSource</tt>, relative to <tt>myApp</tt>. The object bound with the name <tt>myDataSource</tt> in this example happens to be a data source home reference. The whole name <tt>myApp/myDataSource</tt> is relative to the initial context, which you can view as a starting place when performing naming operations.</p>
|
||
|
|
|
||
|
|
<p>You can access and manipulate the name space through a name server. Users of a name server are referred to as naming clients. Naming clients typically use the Java Naming and Directory Interface (JNDI) to perform naming operations. Naming clients can also use the Common Object Request Broker Architecture (CORBA) CosNaming interface. </p>
|
||
|
|
|
||
|
|
<p>Typically, objects bound to the name space are resources and objects associated with installed applications. These objects are bound by the system, and client applications perform lookup operations to obtain references to them. Occasionally, server and client applications bind objects to the name space. An application can bind objects to transient or persistent partitions, depending on requirements.</p>
|
||
|
|
|
||
|
|
<p>In J2EE environments, some JNDI operations are performed with java: URL names. Names bound under these names are bound to a completely different name space which is local to the calling process. However, some lookups on the java: name space may trigger indirect lookups to the name server. </p>
|
||
|
|
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|